Meridio. Installation Guide

Transcription

1 Meridio Installation Guide

2 Document date: February 2008 Document version: 8/0 Meridio version: 5.1 Meridio is a registered trademark of Meridio Limited. Meridio is developed by Meridio Limited. Copyright Meridio Limited. Although Meridio endeavours to ensure that the information in this document is correct and fairly stated, it cannot accept liability for any error or omission. Further, Meridio products and services are under continuous development, and it is important to check with Meridio that a document contains fully up-to-date material. This document does not form part of a contract or licence unless expressly agreed. Meridio uses the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Rights in other trademarks reside with their respective owners. For further information on Meridio see our World Wide Web home page at:

3 Table of Contents Welcome 1 Audience 1 About This Guide 1 What s New 3 Product Support 3 Document Conventions 3 Chapter 1 Introduction to Meridio 5 Key Concepts 5 Architecture 5 Users and Groups 6 Access Control 6 Properties 6 Tasks 7 Templates 7 Backups 7 Archives 7 Document Management Concepts 7 Containers 7 Documents and Versions 8 Records Management Concepts 8 The Meridio Fileplan 8 Disposal 9 Physical Items 9 Protective Markings 10 Holds 10 Chapter 2 Meridio Architecture 11 Basic Architecture Model 12 Simple Architecture Models 13 Meridio Discovery Mechanism 14 Chapter 3 Installation Considerations 15 Supported Software Platforms 15 Software and Network Considerations 19 Meridio Version Numbers 19 Support 19 Windows Event Log 19 Enabling Network Protocols for SQL Server Domain Users Configuration 20 Storage Management 20 Architecture 21 Key Concepts 22 Constraints 25 Recommendations 26 Table of Contents i

4 Chapter 4 Meridio Server Database Only Installation 28 Installation 28 After Installation 33 Chapter 5 Meridio Server Content Server Installation 34 Installing a Meridio Content Server With a Database 34 After Installation 39 Installing a Meridio Content Server Without a Database 40 After Installation 44 Chapter 6 Meridio Server Application Server Installation 45 Installing a Meridio Application Server With a Database 45 After Installation 50 Installing a Meridio Application Server Without a Database 51 After Installation 54 Chapter 7 Meridio Records Management Database Upgrade 55 Installation 55 Hiding Parts in Meridio Records Management 56 Chapter 8 Meridio Administration Installation 57 Chapter 9 Meridio SOAP Installation 58 Before Installation 58 Shared Download Location 58 Web Service Extensions 58 Installation 58 After Installation 62 The Meridio SOAP API Endpoint 62 Security Issues 62 Chapter 10 Meridio Web Services Installation 64 Before Installation 64 Web Service Extensions 64 Installation 64 After Installation 67 Chapter 11 Meridio for Web Users Installation 68 Before Installation 68 Web Service Extensions 68 Installation 68 After Installation 71 Chapter 12 Meridio for Microsoft SharePoint 2003 Installation 72 Before Installation 72 Software Requirements 72 Network Requirements 72 Installation 73 Table of Contents ii

5 After Installation 75 Configuring Meridio Document Store Searching 75 Meridio Site Installer 76 Modifying Meridio for Microsoft SharePoint 77 Chapter 13 Meridio for Microsoft SharePoint 2007 Installation 79 Before Installation 79 Software Requirements 79 Network Requirements 79 Installing Meridio for Microsoft SharePoint Meridio Configuration Wizard 81 After Installing Meridio for Microsoft SharePoint 85 Deploying Meridio for Microsoft SharePoint 85 Activating Meridio Web Application Features 85 Installing Meridio Search Protocol Handler 86 After Installing Meridio Search Protocol Handler 87 Uninstalling Meridio for Microsoft SharePoint 89 Chapter 14 Configuring Web Services for Database Access 90 Configuring SQL Authentication with Login Credentials as Plain Text 91 Configuring SQL Authentication by Encrypting Login Credentials in the Registry 91 Configuring Windows Authentication by Encrypting Login Credentials in the Registry 92 Configuring SQL Server 92 Configuring Meridio Services 92 Configuring Meridio Web Services 92 Configuring Windows Authentication Using the Application Pool Account 93 Chapter 15 Unified and Explicit Login 95 Unified Login 95 Configuring Unified Login for Meridio Server 96 Configuring Unified Login for Meridio SOAP 96 Configuring Unified Login for Meridio Web Services 97 Configuring Unified Login for Meridio for Web Users 98 Configuring Meridio for Microsoft SharePoint 100 Configuring Delegation 101 Explicit Login 101 Configuring Explicit Login for Meridio Server 102 Configuring Explicit Login for Meridio SOAP 102 Configuring Explicit Login for Meridio Web Services 102 Configuring Explicit Login for Meridio for Web Users 102 Chapter 16 Meridio Web Services Configuration Settings 104 Regional Settings 104 File Transfer and Launching 104 DIME Configuration 105 UNC Configuration 106 Size Limit 106 Table of Contents iii

6 Timeouts 107 IIS Security Settings 109 Client Access to Meridio Web Services 109 Chapter 17 Meridio for Web Users Configuration Settings 110 Regional Settings 110 File Transfer and Launching 110 DIME Configuration 111 UNC Configuration 111 Size Limit 112 Timeouts 112 Security Settings 113 Meridio for Web Users Security Settings 113 IIS Security Settings 114 Restricting File Types 114 Miscellaneous Meridio for Web Users Settings 115 Meridio for Web Users View State Settings 115 Configuring the Timeout for Temporary Files 115 Configuring Meridio for Web Users to Accept < and > Characters 115 Changing the Number of Users/Groups Displayed 116 Configuring Federated Search 116 Running Meridio Web Services as a Remote Web Service 118 Modifying Icons for Meridio for Web Users 118 Chapter 18 Meridio for Microsoft SharePoint Configuration Settings 120 Meridio for Microsoft SharePoint 2007 Configuration 120 Meridio Site Features 120 Meridio Storage Policy 121 SharePoint Single Sign-On Authentication 121 Selecting Meridio Properties to Display on the Search Screen 122 Web Configuration Settings 123 Configuring Meridio for Microsoft SharePoint for a WSS Installation 127 Configuring Access to Multiple Systems 127 Configuring Links to Other Systems 127 Chapter 19 Initial System Configuration Tasks 130 Network Configuration 130 Security Issues 130 Configuration 130 Meridio on SQL Server Enabling SQL Mail Stored Procedures 131 System Administration Tasks 132 Chapter 20 Upgrading Meridio 134 Upgrading Meridio Server 134 Performing the Upgrade 135 Table of Contents iv

7 Upgrading Meridio for Microsoft SharePoint Upgrading Meridio for Microsoft SharePoint Upgrading Meridio for Microsoft SharePoint 2003 to Meridio for Microsoft SharePoint Gradual Upgrades 142 Content Migration Upgrades 145 Chapter 21 Uninstalling Meridio 148 Uninstalling Meridio Server 148 Uninstalling Meridio Administration 149 Uninstalling Meridio SOAP 149 Uninstalling Meridio Web Services 149 Uninstalling Meridio for Web Users 149 Chapter 22 Silent Installations 150 Silent Installations for Meridio Products Which Run from Setup.exe 150 Silent Uninstallations for Meridio Products Which Run from Setup.exe 152 Silent Installations for Meridio Products Which Run from.msi Files 152 Silent Uninstallations for Meridio Products Which Run from.msi Files 153 Appendix A Meridio Server Folder Hierarchy 154 Appendix B Registry Entries and System Variables 156 Registry Entries 156 Meridio Version Key 156 Server Configuration Entries 156 Event-Logging Entries 164 Uninstallation Entries 164 System Variables 165 Appendix C Run-time Service Dependencies 166 Appendix D Direct Binding 168 Appendix E Improving Performance 170 Glossary 171 Table of Contents v

8 Welcome Audience This guide is intended for use by system administrators and others who need to install, configure, uninstall or upgrade Meridio systems. The following Meridio components are detailed in this guide: Meridio Server Meridio Records Management Database Upgrade Meridio Administration Meridio SOAP Meridio Web Services Meridio for Web Users Meridio for Microsoft SharePoint Information about installing other Meridio applications, including Meridio Audit Migration, Meridio Reporting Services, Meridio for Microsoft Outlook and Meridio for Desktop Applications, can be found in the relevant guide. If you are installing Meridio in a clustered environment, see Installing Meridio in a Clustered Environment. If you wish to configure Meridio systems for replication, see Meridio Replication Administration Guide. About This Guide The guide is organised into chapters and appendices as follows: Chapter 1, Introduction to Meridio, introduces Meridio document and records management concepts. Chapter 2, Meridio Architecture, describes some example Meridio architectures, and explains the discovery mechanism used by Meridio client applications to contact the Meridio Server. Chapter 3, Installation Considerations, lists the software, network and hardware requirements for installing Meridio components. Chapter 4, Meridio Server Database Only Installation, details how to install a database-only Meridio Server. Chapter 5, Meridio Server Content Server Installation, details how to install a Meridio Content Server, with and without a database. Chapter 6, Meridio Server Application Server Installation, details how to install a Meridio Application Server, with and without a database. Chapter 7, Meridio Records Management Database Upgrade, details how to install the Meridio Records Management Database Upgrade. Welcome 1

9 Chapter 8, Meridio Administration Installation, details how to install Meridio Administration. Chapter 9, Meridio SOAP Installation, details how to install Meridio SOAP, which is required for an installation of Meridio Web Services. Chapter 10, Meridio Web Services Installation, details how to install Meridio Web Services, which includes Meridio for Web Users. Chapter 11, Meridio for Web Users Installation, details how to install Meridio for Web Users. Chapter 12, Meridio for Microsoft SharePoint 2003 Installation, details how to install Meridio for Microsoft SharePoint It also describes how to install Meridio for Microsoft SharePoint on additional websites. Chapter 13, Meridio for Microsoft SharePoint 2007 Installation, details how to install Meridio for Microsoft SharePoint It also describes how to install Meridio for Microsoft SharePoint on additional websites. Chapter 14, Configuring Web Services for Database Access, explains the different methods of configuring Meridio Web Services for access to the Meridio database. Chapter 15, Unified and Explicit Login, describes how to configure unified login, used to log users in to Meridio with their Windows login, and how to configure explicit login, which requires users to log in to Meridio with a separate Meridio login. Chapter 16, Meridio Web Services Configuration Settings, describes the configuration settings for Meridio Web Services. Chapter 17, Meridio for Web Users Configuration Settings, describes the configuration settings for Meridio for Web Users. Chapter 18, Meridio for Microsoft SharePoint Configuration Settings, describes the configuration settings for Meridio for Microsoft SharePoint. Chapter 19, Initial System Configuration Tasks, summarises the administration tasks which must be performed for a new Meridio system. Chapter 20, Upgrading Meridio, describes how to upgrade existing Meridio Server and Meridio for Microsoft SharePoint 2003 installations. Chapter 21, Uninstalling Meridio, details how to uninstall Meridio components. Chapter 22, Silent Installations, describes how to run silent installations for Meridio components. Appendix A, Meridio Server Folder Hierarchy, describes the folder structures in which the Meridio Server is installed. Appendix B, Registry Entries and System Variables, describes the registry entries and system variables that control the settings of the Meridio Server. Appendix C, Run-time Service Dependencies, explains how the various Meridio services depend on one another. Appendix D, Direct Binding, describes how to configure direct binding. Appendix E, Improving Performance, lists some changes that can be made to optimise the performance of ASP.NET for Meridio Web Services, for configurations with multiple network cards. It also contains a Glossary. Welcome 2

10 What s New New in Meridio 5.1: Meridio Content Search service has been replaced by IDOL content search services (Meridio AutonomyIDOL, Meridio DIH, Meridio DAH, Meridio OmniGroupServer); changes include those to the procedures for installing Meridio Server. IDOLConfigUtility.exe must be run after installing Meridio Content and Application Servers. Meridio Server requires Microsoft.NET Framework 2.0; Meridio Web Services and Meridio for Web Users require Microsoft.NET Framework 2.0 with Service Pack 1. It is possible to run a content migration upgrade for Meridio for Microsoft SharePoint 2003 to Meridio for Microsoft SharePoint 2007 (see page 145). Product Support See for the currently supported platforms and Meridio versions. Document Conventions The following table describes the formatting conventions used in this guide. bold button cross-reference italic monospace sans serif Used for a Meridio property or the dialog box or web page item which references the property, such as a check box, text field or drop-down list. Also used for other objects on dialog boxes and web pages and for menu commands. Also indicates keywords in the guide. Used for the names of buttons on a dialog box or web page, e.g. OK. Indicates a reference to another document or to a chapter or section of the current document. Used for emphasis, or to indicate that a section of code or part of a filename or registry key is variable. Also used to indicate a user or group name, the state of an object, or a required permission or privilege. Used for sections of code, including XML. Also used for registry keys. Indicates the name of a file or folder, e.g. C:\Meridio, or the name of a keyboard key or key combination, e.g. Enter or Ctrl+C. Indicates a note. Indicates a warning. Welcome 3

11 Indicates a tip. Welcome 4

12 CHAPTER 1 Introduction to Meridio The Meridio family of edrm (Enterprise Document and Records Management) products enables its users to share a common system for the safe storage of documents and records. In a Meridio system, documents and records are secured in the document store against accidental deletion or unauthorised access. Users access Meridio through a number of client applications, such as Meridio for Web Users or Meridio for Microsoft Outlook. Meridio system administration tasks are performed using the Meridio Administration application and also with the Meridio for Web Users client. A Meridio system can be configured in the following ways: document management only document and records management Key Concepts The concepts introduced in this section are relevant to all configurations of Meridio, both with and without records management. Architecture When a client user requests a transaction, the Meridio Server process manages all the communications. If storage management is used, the Meridio Storage Agent manages the storage of documents on the server. If a user wishes to perform searching on the contents of documents, the IDOL content search services scan the Meridio Indexes. Several Meridio Servers each running on separate physical machines can share the same SQL database and document store. This is configured during installation. With this configuration, one Meridio Server is installed as a Content Server and the others are installed as Application Servers. The Meridio Indexes and document store reside on the Content Server machine, and the Storage Agent, Scheduler, server utilities, and tasks run on the Content Server machine. The Meridio Database can reside on the Content Server machine, an Application Server machine, or a separate machine altogether. Application Servers are added to a Meridio system in order to spread the workload. See Chapter 2, Meridio Architecture, for more information about Meridio system architecture. A server administrator can use Meridio Administration to carry out a large number of the system management tasks. Other administration tasks, including the creation of all records management environment data, are performed in Meridio for Web Users. See Meridio for System Administrators for information about these. A number of server utilities enable archiving, backups, and restores to be performed. These utilities reside on the Content server machine. Information about various events in a Meridio system is recorded in an Audit Database. The activity in a Meridio system can be monitored by running reports against this database. Several standard reports are provided with Meridio. The Audit Migration service is responsible for importing event details into the database from log files Chapter 1 - Introduction to Meridio 5

13 produced by each server. See Meridio Auditing Administration Guide for more information. Typically, the Meridio components are installed at the same, central location. However, widely distributed organisations may install a Meridio Remote Content Server at one or more remote locations. The Meridio Remote Content Server caches document content that has been previously retrieved by users at a remote site, so reducing access times for subsequent accesses to the content at that site and reducing network load. See Meridio Remote Content Server Administration Guide for more information. Users and Groups To use a Meridio system, you must have a user account, with a unique username and a password. If you wish to use more than one Meridio system, you must have a user account on each. Depending on the configuration of the Meridio system, you may be logged in to Meridio automatically without needing to enter a username or password once you have logged in to Windows. Users may be organised into groups. Each user is a member of at least one group (the Public group, created during the installation of the Meridio system), but can be a member of several. Groups may correspond to different combinations of people within an organisation, based for instance on rank, department or location. Users and groups are allocated privileges, which determine what actions they can perform in a Meridio system. For example, the Add Documents privilege is required for a user to be able to add a document to Meridio. Access Control Each item in Meridio (containers, documents, classes, folder and records) can have an access control list which contains the permissions assigned to users and groups. The permission assigned to each user or group determines what level of access they have for the item. For example, Read access is required for a user to be able to view the properties of a document, but Manage access is required to change the properties. Some properties can also be edited if you have Amend access and the system administrator has enabled the extended Amend permission. If a user is the owner of an item, or has the Manage privilege for the item type (for example, Manage Containers), their access level for the item is Manage, even if the access control list for the item does not explicitly assign them the Manage permission. Properties Each Meridio item has a set of properties which contains information about it. Some of the properties have values assigned to them by the Meridio system; for others, the user enters the value when creating the item. The properties assigned to each item type during the installation of the Meridio system are known as fixed properties. Additional properties can be defined by the system administrator for certain items - these are known as custom properties. Chapter 1 - Introduction to Meridio 6

14 Document categories can be created by the system administrator, and given a particular set of custom properties. When documents are added to Meridio, they can be assigned a category; the custom properties of the category are then associated with the document. Tasks Using Meridio Administration, an Admin user can schedule administrative tasks to run immediately or at specified dates and times, and can monitor their progress. The actual tasks run on the server machine, managed by the Meridio Scheduler service. Tasks include enforcing storage policies, optimising the database, and synchronising Meridio user and group information with LDAP directories. Templates Meridio facilitates the bulk addition of documents, groups and users to the system through the use of customisable templates. Backups Data on the system can be transferred to offline storage by means of a backup. A full backup copies all the data on the system, including documents, properties, and content search information. An incremental backup copies only data that has changed since the last full backup. Archives Old versions of documents may be moved to an offline archive to conserve disk space. The backup and archiving processes are performed by Meridio Server utility programs. Users who wish to bring an archived version back onto the system can do so by issuing a request to reclaim the version (this is done from a Meridio client application). The progress of all these processes may be monitored using Meridio Administration. Document Management Concepts The items which can be added to a document management-only Meridio system are: containers documents Containers and documents are added using any of the Meridio clients. See the relevant user guides for more information. Containers A container is the Meridio equivalent of a Windows folder; it holds references to documents, stored searches and other containers. Containers are virtual items whose structure does not reflect the physical storage of documents; they hold only references to documents, not the actual documents themselves. Each Meridio user has a personal container hierarchy, in which My Workspace is the top level. The user can share containers in My Workspace, so that users with the appropriate access control permissions can access the containers contents. Chapter 1 - Introduction to Meridio 7

15 Documents and Versions In Meridio, a document refers to an item which is stored in electronic format, such as a word-processing document, message, spreadsheet or image. When a user saves a document to Meridio, or locates a document by searching the Meridio system, a document reference can be placed in one or more containers for easy access to the document. Document references can be deleted from a container at any time. However, the document itself is not removed from the Meridio system unless it is marked for deletion and then purged from the system by an administrative task. For a Meridio system with records management, document references can also be placed in a folder. Meridio maintains control over versions of documents. A check-out, check-in system is used to avoid simultaneous updates of a document by more than one user. Each document has an associated policy, which determines the criteria for when versions are offlined. If a document version has been archived offline, users can issue a request to reclaim the version. Records Management Concepts Additional items that can be added to a Meridio system enabled for records management are: classes folders parts records The Meridio Fileplan The Meridio Fileplan is a hierarchy of classes, folders and parts, similar to Windows folders, into which records are declared and document references are placed. Only classes can be added to the top level of the Fileplan. Classes can contain both classes and folders. Folders contain parts, which contain documents and records. The classes and folders in the Fileplan are visible to and can be accessed by any user with the appropriate security (access control and protective markings). The security for a folder also applies to its parts. Documents can be declared as electronic records, which are stored in folders in the Fileplan. Once a document has been declared as an electronic record, further modifications to its content are not possible. Each record is associated with a particular folder part, and references to it can exist in other parts or in containers in a user s My Workspace. Chapter 1 - Introduction to Meridio 8

16 The following table lists the items that can be added and viewed in each of the Meridio clients. See the relevant user guides for more information. Client Class Folder Part Record Meridio for Web Users View, add, manage View, add, manage View, add, manage View, declare, manage Meridio for Microsoft SharePoint View, add, manage View, add, manage View, add, manage View, declare, manage Meridio for Microsoft Outlook View, manage View, add (electronic folders only), manage View, declare, manage Meridio for Desktop Applications View, manage View, manage View, declare, manage Disposal Each folder, part and record in the Meridio Fileplan can have a disposal schedule chain, which determines the length of time that the records it applies to are retained. It also determines what happens to the records (or folders or parts) at the end of the retention period. A class can be assigned a disposal schedule chain, but this applies to the folders, parts or records in the class s hierarchy rather than to the class itself. Each disposal schedule chain consists of one or more disposal schedules; each disposal schedule consists of an instruction and a retention period, for example, Review folder 6 months after closing. Disposal schedule chains are associated with a particular type of item - folder, part or record - and are inherited from their parent item. Explicit disposal schedule chains can also be set for individual items. Disposal schedule chains can only be applied to items which match the type of item with which they are associated. For example, if a folder has a disposal schedule chain of type record, it has no effect on the folder, but any records subsequently declared within the folder inherit its disposal schedule chain. Disposal schedule chains are inherited even if the parent class or folder does not have its Inherit option selected. Physical Items The Meridio system can be used to maintain and track access to physical items such as hard-copy documents. Physical folders and physical parts can be added to Meridio to represent folders or other physical items which exist outside Meridio. Hybrid folders and parts can also be created; these refer to both Meridio items and physical objects. Physical markers can be added to electronic or hybrid folders to represent individual external records. Chapter 1 - Introduction to Meridio 9

17 The movement of physical items can be tracked by using the physical archive and its request and check-out, check-in functionality, in a similar way to how a library records movement of its books. Protective Markings Protective markings are a further level of security, in addition to access control. A protective marking (a word or phrase taken from a pre-defined list) can be applied to an individual class, folder, record or document. An item marked in this way is only accessible to users who have been granted the same protective markings as those applied to the item. Holds A hold, when applied to an item in Meridio, prevents the deletion or disposal of that item. Holds are usually applied for legal reasons. Chapter 1 - Introduction to Meridio 10

18 CHAPTER 2 Meridio Architecture A Meridio system comprises the following components: Meridio Server: Meridio Database (DMSDB) a SQL Server database which stores all the metadata relating to Meridio objects such as documents, users, groups and backups. The first installation of the database is for document management only; it can also be upgraded for records management. Meridio Content Server stores document and record content, manages full-text indexes of the content, and runs the Meridio Server, Meridio Scheduler, Meridio Storage Agent and IDOL content search services. Meridio Application Server runs the Meridio Server service. Meridio SOAP sits between the Meridio Web Services and a Meridio Server. Meridio Web Services used by Meridio clients; also the main custom development API. Meridio Audit Migration comprises the meridioaudit database and the Meridio Audit Migration service. A reporting tool is also available. See Meridio Auditing Administration Guide for more details. Meridio for Web Users ASP.NET web application which provides access to Meridio. Meridio for Microsoft SharePoint (optional) integrates with Microsoft SharePoint to provide access to Meridio. other Meridio clients (optional) Meridio for Microsoft Outlook, Meridio for Desktop Applications, Meridio Offline Synchroniser and other Meridio client applications connect to the Meridio Server via a discovery mechanism (see page 14). Meridio Reporting Services (optional) integrates with SQL Server Reporting Services to provide Meridio reports. See Meridio Reporting Services Administration Guide for more details. Meridio Enterprise Document Capture (optional) integrates with Microsoft Exchange Server and Office Communications Server to automatically import messages and instant messages into Meridio. A stand-alone Import Wizard is also available. See Meridio Enterprise Document Capture Administration Guide for more details. If you wish to install a Meridio database or content or application servers in a clustered SQL environment, see Meridio in a Clustered Environment. If using replication, see Meridio Replication Administration Guide. If using a remote content server, see Meridio Remote Content Server Administration Guide. Chapter 2 - Meridio Architecture 11

19 Basic Architecture Model The following illustration shows a basic three-machine configuration for a Meridio system. Meridio for Microsoft SharePoint (Chapter 12, Meridio for Microsoft SharePoint 2003 Installation, and Chapter 13, Meridio for Microsoft SharePoint 2007 Installation ) and Meridio Reporting Services can be installed on additional machines if required. Meridio Audit Migration should also be installed on an additional machine. It is recommended that the meridioaudit database is installed on a separate SQL Server to the Meridio Database. See Meridio Auditing Administration Guide for more details. For further resilience, a clustered SQL Server instance is recommended, and also two instances of Machine B and two of Machine C. For this architecture, potential performance enhancements are possible if direct binding is used for Machine C. See Appendix D, Direct Binding, for more information. The following table lists the components to be installed on each machine for the illustrated system. Machine Component Installation Instructions Machine A Meridio Database Chapter 4, Meridio Server Database Only Installation Machine B Meridio Content Server Chapter 5, Meridio Server Content Server Installation Machine C Meridio Application Server Meridio SOAP Meridio Web Services Chapter 6, Meridio Server Application Server Installation Chapter 9, Meridio SOAP Installation Chapter 10, Meridio Web Services Installation Chapter 2 - Meridio Architecture 12

20 If you are going to use multiple servers in your Meridio system, it is very important to synchronise the system clocks on each server machine, to the nearest second. Otherwise, problems may occur with the Scheduler service and other Meridio components. Problems may also occur if the maximum number of connections to your SQL Server database is less than the total number of Meridio services in the system (not including Meridio Web Services), as each server-side service must have its own connection to the Meridio database. Simple Architecture Models For a simpler system, for example with a small number of users, fewer machines can be used. Two-Machine Configuration The following table lists the components to be installed on each machine for a twomachine configuration. Machine Component Installation Instructions Machine A Meridio Database Chapter 4, Meridio Server Database Only Installation Machine B Meridio Content Server Meridio SOAP Meridio Web Services Chapter 5, Meridio Server Content Server Installation Chapter 9, Meridio SOAP Installation Chapter 10, Meridio Web Services Installation Single-Machine Configuration The following table lists the components to be installed for a single-machine configuration. Machine Component Installation Instructions Machine A Meridio Database and Content Server Meridio SOAP Meridio Web Services Chapter 5, Meridio Server Content Server Installation Chapter 9, Meridio SOAP Installation Chapter 10, Meridio Web Services Installation Chapter 2 - Meridio Architecture 13

21 Meridio Discovery Mechanism Meridio uses Active Directory to generate and maintain a list of Meridio systems that are available on a network as follows: 1. The Meridio Server publishes its network information in the Active Directory using the RPC (Remote Procedure Call) Locator service. 2. The following Meridio client applications retrieve a list of available Meridio Servers from Active Directory, and store the list in an XML cache file: Meridio Administration Meridio for Microsoft Outlook Meridio for Desktop Applications Clients which use Meridio Web Services to connect to Meridio Servers, such as Meridio for Web Users, use an XML cache file which is maintained for Meridio SOAP. CachedMeridioSystems File The file is named CachedMeridioSystems{systeminformation}.xml and is located in the following Windows folder for Meridio clients (on the machine on which the client is installed): Windows XP \Documents and Settings\YourUser\Local Settings\Application Data Windows Vista \Users\YourUser\AppData\Local The cache file used by Meridio SOAP is placed in one of the following locations on the machine on which Meridio SOAP is installed, if unified login is used or the MeridioSOAP virtual directory does not have a domain account for anonymous access: \Windows\temp \Documents and Settings\Default User.WINDOWS\Local Settings\Application Data If the MeridioSOAP virtual directory is configured with a Windows domain account for anonymous access, the cache file is placed in \Documents and Settings\DomainAccount\Local Settings\Application Data. The default expiry period of this file is 24 hours, but this can be changed by creating a String entry, SystemListCacheTimeout, in the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Meridio Ltd\Meridio Shared The value can be set to: 0 to maintain the cached list indefinitely the number of seconds that the cached list should be maintained, e.g to expire it hourly The XML file can be deleted from the client machine to force the client application to recreate the cached list from Active Directory. This is recommended if a Meridio system that is known to be available is not displayed in the client s system list. Chapter 2 - Meridio Architecture 14

22 CHAPTER 3 Installation Considerations This chapter describes the issues that must be taken into consideration before installing Meridio, including the pre-requisites for third-party software, and how Meridio storage management functionality can be used. Meridio Server cannot be installed on an Intel Itanium platform, except for a databaseonly installation. Supported Software Platforms The following table shows the third-party software that must be on your computer before the installation of each component takes place. For the most up-to-date list of the currently supported platforms and Meridio versions, see Meridio Component Meridio Server Software Required Windows Server 2003 or Windows Server 2003 R2 32-bit (with Service Pack 1 and all Microsoft Windows critical updates) and 64-bit # platforms Microsoft Internet Explorer version 6.0 (with Service Pack 1) or later Microsoft Data Access Components (MDAC) version 2.5 or later Microsoft WSE 2.0 (with Service Pack 3) available on the Meridio installation CD Microsoft.NET Framework 2.0 Notes: The Remote Procedure Call (RPC) Locator service should be enabled and configured for automatic start. The version of MDAC should be the appropriate version for the version of SQL Server installed on the Meridio Database machine. See for further details. # The 64-bit platform refers to the x64 edition of Windows Server 2003 in WOW64 emulation mode. Chapter 3 - Installation Considerations 15

23 Meridio Component Meridio Database Meridio Administration client Meridio SOAP Software Required Windows Server 2003 or Windows Server 2003 R2 32-bit (with Service Pack 1 and all Microsoft Windows critical updates) and 64-bit # platforms Microsoft SQL Server 2000 (with Service Pack 4) or SQL Server 2005 (with Service Pack 2) Notes: If installing the Meridio Developer version rather than the Full version, SQL Server Desktop Engine (2000) or SQL Server Express (2005) can be used instead of the full SQL Server product. Before installing SQL Server, ensure that the locale and language settings on your system match. (See Regional Settings / Regional Options in your Windows Control Panel.) During installation of SQL Server, select Mixed Mode as the authentication mode. Use all other default choices offered by the installer. Windows XP Professional, Windows Vista, Windows Server 2003 or Windows Server 2003 R2 (with Service Pack 1 and all Microsoft Windows critical updates) Windows Server 2003 or Windows Server 2003 R2 32-bit (with Service Pack 1 and all Microsoft Windows critical updates) and 64-bit # platforms Internet Information Services 6.0 (including ASP.NET) Microsoft Internet Explorer version 6.0 (with Service Pack 1) or later Microsoft WSE 2.0 (with Service Pack 3) available on the Meridio installation CD Notes: The following services should be enabled and configured for automatic start: IIS Admin HTTP SSL WWW Publishing Service # The 64-bit platform refers to the x64 edition of Windows Server 2003 in WOW64 emulation mode. # The 64-bit platform refers to the x64 edition of Windows Server 2003 in WOW64 emulation mode. Chapter 3 - Installation Considerations 16

24 Meridio Component Meridio Web Services Meridio for Web Users Software Required Windows Server 2003 or Windows Server 2003 R2 32-bit (with Service Pack 1 and all Microsoft Windows critical updates) and 64-bit # platforms Internet Information Services 6.0 (including ASP.NET) Microsoft Internet Explorer version 6.0 (with Service Pack 1) or later Microsoft WSE 2.0 (with Service Pack 3) available on the Meridio installation CD Microsoft Data Access Components (MDAC) version 2.5 or later Microsoft.NET Framework 2.0 (with Service Pack 1) Notes: The following services should be enabled and configured for automatic start: IIS Admin HTTP SSL WWW Publishing Service Windows Server 2003 or Windows Server 2003 R2 32-bit (with Service Pack 1 and all Microsoft Windows critical updates) and 64-bit # platforms Internet Information Services 6.0 (including ASP.NET) Microsoft Internet Explorer version 6.0 (with Service Pack 1) or later Microsoft WSE 2.0 (with Service Pack 3) available on the Meridio installation CD Microsoft Data Access Components (MDAC) version 2.5 or later Microsoft.NET Framework 2.0 (with Service Pack 1) Notes: The following services should be enabled and configured for automatic start: IIS Admin HTTP SSL WWW Publishing Service # The 64-bit platform refers to the x64 edition of Windows Server 2003 in WOW64 emulation mode. Chapter 3 - Installation Considerations 17

25 Meridio Component Meridio for Microsoft SharePoint Software Required Windows Server 2003 or Windows Server 2003 R2 (with Service Pack 1 and all Microsoft Windows critical updates) 32-bit platforms only Internet Information Services 6.0 (including ASP.NET) Microsoft Internet Explorer version 6.0 (with Service Pack 1) or later One of the following Microsoft SharePoint installations: Microsoft SharePoint Portal Server (Service Pack 1 or 2) Microsoft Windows SharePoint Services 2.0 (Service Pack 1 or 2) Microsoft Office SharePoint Server 2007 (MOSS) Microsoft Windows SharePoint Services 3.0 Microsoft WSE 2.0 (with Service Pack 3) available on the Meridio installation CD Microsoft Data Access Components (MDAC) version 2.5 or later Notes: The following services should be enabled and configured for automatic start: IIS Admin HTTP SSL WWW Publishing Service You must have Administrator privileges on your computer before attempting to install Meridio components. If Microsoft.NET Framework 1.1 is not already on the computer, the Meridio installers listed in the previous table will install it. With the exception of a database-only Meridio Server installation, WSE 2.0 with Service Pack 3 must be installed on any machines on which you wish to install Meridio Server, Meridio SOAP, Meridio Web Services, Meridio for Web Users or Meridio for Microsoft SharePoint. This can be installed from the Meridio CD. Chapter 3 - Installation Considerations 18

26 Software and Network Considerations The following software and network issues must be taken into account. Meridio Version Numbers All server-side components in a Meridio system must have the same version number. Therefore, for instance, you cannot install a Content Server on one computer and associate it with a different version of the Database on another computer. You cannot install a Server or Database if there is already one of these components with a different version number on the same computer. However, it is possible to upgrade an older version of Meridio without losing either document content or information in the Database. See Chapter 20, Upgrading Meridio, for more information. Support The Meridio services must be able to contact an IIS SMTP service if they are to provide support. The IIS SMTP service can run either on the Meridio Server machine, or on another machine on the local network. Any machine which has a Meridio Content Server installed must also have either MAPI or Microsoft Outlook installed and configured for use, in order for.msg files to be correctly indexed. Windows Event Log The event log must be made accessible (with write permissions) for all Meridio users. Edit the following registry key, and add the SID for the Everyone group, e.g. (A;;0x3;;;S ): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\Custom SD Enabling Network Protocols for SQL Server 2005 By default, SQL Server 2005 does not allow remote connections over the network. For a distributed Meridio architecture, the network protocols must be enabled. To enable network protocols: 1. Launch the SQL Server Configuration Manager (Start All Programs Microsoft SQL Server 2005 Configuration Tools SQL Server Configuration Manager). 2. Expand the SQL Server 2005 Network Configuration Protocols for MSSQLSERVER node. Chapter 3 - Installation Considerations 19

27 3. Right-click on TCP/IP and select Enable from the shortcut menu. 4. Restart the MSSQLSERVER service. If the Meridio database (DMDSB) and Meridio Audit database (meridioaudit) are on different SQL Server 2005 instances, this procedure must be performed on each. Domain Users Configuration It is recommended that domain user accounts are configured for the following: The account under which Meridio Server services will run, specified during a Meridio Server installation. This account can also be used for Kerberos security with unified login, and as the account for anonymous access specified on Meridio Web Services virtual directories. This account will be created as a Meridio user during the Meridio Server installation. The account under which the application pool for Meridio Web Services will run. This account must not be a Meridio user. For both accounts, the following are recommended: local administrator on the relevant machines, and, if possible, member of the Domain Admins group Log on as service policy on the relevant machines members of the IIS_WPG group on the machines on which Meridio SOAP and Meridio Web Services are installed Storage Management Meridio has evolved a highly advanced storage architecture in support of highly configurable storage management functionality. This section describes the concepts of Chapter 3 - Installation Considerations 20

28 storage management; the specific functionality is described in Chapter 4, Storage Management, of Meridio for System Administrators. Meridio s storage management capabilities have been developed in response to a specific need, which is to allow administrative control over which physical devices the individual items of content reside on. This includes: migration across a range of devices in response to time and events maintaining multiple copies of any item of content on different devices using devices that are shared among all content servers Migration across a range of devices allows installations to deploy a range of heterogeneous storage devices and to control which content resides on which type of device at any specific time, in support of business storage policy. The combination of maintaining multiple copies of items and using shared devices provides resilience, both against the possibility of failure of a specific device and against the failure of a content server. Architecture Meridio s storage management capabilities follow the principle of augmentation rather than replacement. In other words, the addition of new capabilities must not prevent previously installed sites configurations from continuing to work. The following diagram summarises the up-to-date storage architecture. Web Servers Meridio Web Services Mer idio Content Server Meridio Content & Content Indexes Microsoft SQL Server MetaData Mer idio Content Server Meridio Content & Content Indexes NAS device Shared access SAN EMC Centera cluster With this architecture, all the elements below the content servers are optional. The typical processing sequence for content is: 1. A document or record is added to Meridio and its content is placed on one of the disk partitions within one of the content servers. 2. Periodically, a scheduled task called the Enforce Policies task is run. This decides which items of content should be copied to and deleted from which storage devices. These decisions are made in response to administrator-defined configurations. Chapter 3 - Installation Considerations 21

29 3. Once the Enforce Policies task has made its decisions, the Storage Agent carries them out. The Storage Agent is one of the services that runs on each content server. Note that for each item of content, the Storage Agent performs the copies before the deletes. If a copy fails, the remaining activities for that item of content are ignored until the next run of the Enforce Policies task. This is a safety measure to ensure that the Storage Agent never ends up deleting all available copies of an item of content. 4. When a user wishes to retrieve an item of content, the request is routed to the highest priority copy priority is again determined by the administrator-defined configurations. 5. If the highest priority copy is unavailable, the request is rerouted to the next highest priority copy. 6. If the highest priority is on a partition on a specific content server, and if that content server is unavailable, the request is rerouted to an alternative content server. With this architecture, the majority of access to the storage devices occurs through a storage abstraction layer within the services on the content server that interact with storage (the main Meridio Server and the Storage Agent). This layer is extensible so that types of storage device that require special APIs (e.g. EMC Centera) can be supported simply by adding a new DLL onto the content servers and making a simple database change. Providing no new functionality is required, such a change can be made without needing to upgrade Meridio. The content servers partitions as referred to as initial partitions or unmanaged storage and the devices that are under control of the Storage Agent are referred to as managed storage. Key Concepts In order for administrators to be able to effectively define the rules by which the Enforce Policies task decides which items of content belong where, a set of concepts specific to the domain of storage management is required. Every document or record in Meridio has a single associated storage policy from a set of policies defined by the administrator. The policy can be changed at any time. The storage policy defines either how many versions of the document may be held online, or for how long a version may be held online, or both. If it defines how long a version may be held online, the length of time is measured either from when the version was added or when it was last retrieved. In each case, once Meridio decides that a version can no longer be kept online, it (and its associated renditions) will either be archived or deleted. Once archived, if a version is reclaimed, all its associated renditions will be reclaimed with it. The scheduled Enforce Policies task evaluates these factors and decides when versions should be taken offline. The storage policies and the Enforce Policies task are configured using the Meridio Administration client. Using the separate Storage Administration utility, administrators may additionally define storage schedules to be associated with storage policies, where any schedule may be shared among many policies but each policy may only have a maximum of one schedule. Each schedule comprises a set of storage classes. Each storage class contains one or more storage devices, with all devices in a class having or using the same characteristics. Each storage class is given a relative retrieval priority (a positive integer where 0 is the highest priority). Each device may only belong to one class the content server partitions are by default grouped together into a single class called Initial partitions, which cannot be changed. Note that the retrieval priority 0 is Chapter 3 - Installation Considerations 22

30 reserved for initial partitions only. Any class can be included in many storage schedules. Managed storage devices by definition must be able to be shared by all Meridio content servers there is no concept of a device belonging to a content server. If final storage locations are enabled for the system, each class in a storage schedule can be included in the final storage location for versions and renditions to which this schedule applies. Once a version or rendition has content located in the classes included in the final storage location, but not in any other classes, the version or rendition is marked so that it is no longer acted on by the Enforce Policies task. A storage schedule is a completely separate concept from a records management retention/disposal schedule, and the two must not be confused. Similarly, a storage class is a completely separate concept from a records management class. The following diagram illustrates storage classes and schedules. Rapid access High availability 1 High availability 2 Low cost Initial partitions Storage classes Schedule 1 Schedule 2 Schedule 3 Each storage class in a storage schedule has its own unique set of test conditions (condition set). These test conditions are re-evaluated each time the Enforce Policies scheduled task is run, and whenever a condition set evaluates to TRUE, then a copy of any content associated with that schedule (via the document s storage policy) is placed into the associated storage class (if there isn t already a copy there). Therefore, if many sets in a schedule for an item of content evaluate as TRUE, there will be many copies of that item of content made. Any content on a class that is not covered by a TRUE condition set is deleted following re-evaluation. There are two exceptions to this deletion rule: At no time will this mechanism permit every copy of content to be deleted at least one copy must remain somewhere in the system. While an item of content is awaiting content indexing it will not be deleted from its initial partition. Chapter 3 - Installation Considerations 23

31 The exceptions only apply to these mechanisms associated with the storage schedule the older policy mechanisms of version limit and access time continue to operate, deleting all copies of a version as appropriate. The conditions that may be tested for are intended to be extensible to permit storage management to evolve in line with feedback from Meridio s customers and partners. Currently they include: the time since last access (to the content of the version or one of its renditions) the time since creation of the version or rendition to which this content belongs the time since creation of the version that is the parent of this content (i.e. we test the version even if this item of content belongs to a rendition) the time since creation of the document to which this content belongs whether it is the latest version the rendition type the size of the content file the format of the content file (as recognised by Meridio s internal content indexing mechanisms not to be confused with rendition type) TRUE a catch-all condition that always evaluates to TRUE Each condition set defines whether all of its conditions or just one of them needs to be true for the whole set to be considered true (i.e. AND or OR the conditions respectively). Condition set 60 days since content last accessed AND not the latest version of the document AND file format is JPEG Storage classes may only contain devices that are accessible by all content servers (e.g. NAS, EMC Centera, SAN shared access partitions), in order to provide resilience in the event of one content server failing. The exception is the Initial partitions class. This storage class is special in that once content has been deleted from the initial partitions, it can never be copied into them again. Initial partitions can be used purely as an addition cache. Alternatively storage schedules need not be defined, in which case content will simply spend its entire life on content server partitions. Chapter 3 - Installation Considerations 24

32 The relationships between the entities described are presented in the following entityrelationship diagram. Document m 1 Policy m 1 Storage Schedule 1 1 Condition m 1 n Condition Set One condition set for each class within any specific schedule m n Version 1 1 m Rendition Storage Class m n n Content m n m Shared Device m 0..1 Partition m One item of content can have copies on many shared devices, but a maximum of one copy on each shared device (indeed in each storage class). 1 1 Device Type Constraints All storage devices to be used in storage classes, other than initial partitions, must be equally accessible from all content servers. In addition, shared SAN partitions must be accessed through a SAN shared file system and must use the same drive letter on all content servers, i.e. all content servers must be able to write files to the device (which also refers to a logical division of a device such as a partition of a partitioned device), and all servers must be able to read any files on the device. Although NAS and file shares always allow this, the same is not true of all SANs; check with your vendor first. Customers who wish to use SAN storage but cannot comply with the above constraints have two options: To define the SAN partitions as initial partitions only and ignore the advanced storage management functionality. To deploy one or several file servers with non-shared access to the SAN partitions. Each server shares its SAN partitions as UNC shares. Define these shares to Meridio storage management. Meridio only supports shares from file servers or NAS devices running Windows 2000 Server and above. Mapped drive letters are not supported. NTFS devices used by storage management will place content within a directory hierarchy that begins Meridio\Content, that itself is placed directly under the root of the device as defined by the access string. For example, if a directory d:\shares\share1 on a fileserver is set up as a UNC share, then storage management will place all its content somewhere under d:\shares\share1\meridio\content. Chapter 3 - Installation Considerations 25

33 Before defining a device to Meridio, it is essential to appropriately configure the security to be inherited by subdirectories. Note that if the required directories do not exist before defining to Meridio, Meridio will attempt to create them when it wants to copy a file onto the device. With NTFS devices (i.e. drive letter or UNC access), Meridio wants to write under \Meridio\Content. If these directories do not exist, Meridio attempts to create them when it wants to copy to the device. This means that the level above must have its security set appropriately for these directories to inherit. If that is not possible (e.g. because it s a drive letter device and other applications or users need access to that drive also), then you must create \Meridio or \Meridio\Content prior to defining the drive on Meridio, and set the security appropriately on this. This situation is most likely to arise on SAN devices. When using the test condition Since content creation in an environment where Meridio archiving is also performed, note that when archived content is reclaimed, the date and time that this test examines is reset to the date and time of the reclaim rather than the date and time that the content was originally created. When setting up devices in the Storage Administration utility (see Meridio for System Administrators), do not use an equals sign (=) in the device name. The SDK function makefilelink only works against files on initial partitions. Meridio s automated backup is inappropriate for use in a managed storage environment, as it only handles files from initial partitions. A manual or custom backup is required instead; note that any file list generated will not list files from managed storage devices. Recommendations If you wish to define a storage policy for the purposes of storage management features only (i.e. you are not interested in version limited or date-based policies), in the Meridio Administration client, set the policy options to date-based only with the online time as long as possible (999 months 83 years) following the last date accessed. If there s any concern about a document version disappearing after 83 years (remember that record versions will only disappear when/if the record s disposal schedule dictates), then set the offline decision to Archive version. It is important to understand that the more online versions that exist, the greater the workload placed on the Enforce Policies task, which in turn means the greater the load that the task places on the database and general server resources. Use of the date-based limits and especially the version limits is an effective way of limiting the impact on the database and server resources. Set each partition s threshold quite high and have it suspend the partition when the threshold is reached see Chapter 4, Storage Management, in Meridio for System Administrators for more information. Do not, however, set thresholds so high as to have insufficient space for temporary storage. Temporary storage is used during retrieval from non-filesystem storage devices (e.g. EMC Centera). Run the Enforce Partition Thresholds task frequently. If resilience is critical, note the limitations of any resilient storage technologies that you deploy. For example, some storage platforms that provide mirroring do their mirroring asynchronously. This means that the mirror copy is not guaranteed to exist the moment the file has been written to the device. Therefore, the device could fail before the mirror Chapter 3 - Installation Considerations 26

34 copy has been created, and if you are solely relying on that device s technology for your resilience (i.e. if you have no other copies of this content on any other storage classes), then you will have lost all access to that content. This is not meant to dissuade you from deploying such technologies; on the contrary we encourage the use of such technologies where resilience is critical, but be aware of the limitations of any technology deployed and use it appropriately. In the case of the above example, an appropriate configuration would be to ensure that there is a second copy of content on another device, at least for the time period for which you are confident that the mirror will have been created. The Enforce Policies task has been tuned to make judicious use of memory on the SQL Server machine in order to boost performance. However, should there be insufficient memory for its purposes, this could have a significant negative impact on the time that this task takes to run. It is recommended that this task be scheduled to run during a quiet period, and that memory consumption and paging activity on the SQL Server be regularly monitored in order to obtain advance warning should resource consumption creep up over time to the point where it needs to be addressed. If using the test condition Latest Version on a Meridio system where the majority of documents have two or more online versions, arrange your tests if possible such that only the TRUE value is used. This will require less resource consumption by the Enforce Policies task than using the FALSE condition. However, should the majority of documents on the system be single version, then the FALSE value is the more efficient form to use. When defining managed storage devices, if you have one content server that is significantly more powerful than the rest, it may be helpful for all managed devices to be notionally assigned to that server. Chapter 3 - Installation Considerations 27

35 CHAPTER 4 Meridio Server Database Only Installation This chapter describes how to perform a database-only installation of Meridio Server. See Chapter 2, Meridio Architecture, for more information about the different types of Meridio Server. Installation Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. For a non default SQL installation, you must add the following system environment variable on the machine on which you want to install Meridio Server: MERIDIO_SQL_SERVER_INSTANCE Set the value to the name of the SQL Server instance on which you want the Meridio Database (DMSDB) to be installed, in the format Server\Instance. For a non default SQL installation on a 64-bit server, the ODBC data source must be configured using the 32-bit version of the ODBC Data Source Administrator. To install a Meridio Database: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. If the Meridio Server installer reports that Setup has detected a previous installation on your machine that cannot be upgraded directly to 5.1. and you are sure that you are trying to upgrade a 3.0, 3.0 SR-1, 3.0 SR-2, 3.0 SR-3, 3.1, 3.2, 3.3, 3.3 SR-1, 3.3 SR-2, 4.0, 4.1, 4.1 SR-1, 4.2, 4.2 SR-1, 4.2 SR-2, 4.3, 4.3 SR-1, 4.4, 4.4 SR-1, 4.4 SR-2, 5.0 or 5.0 SR-1 release, then support@meridio.com with details of the following registry key version value: HKEY_LOCAL_MACHINE/SOFTWARE/Meridio Ltd/Meridio Server. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. Chapter 4 - Meridio Server Database Only Installation 28

36 4. On the first Setup Type page, select Don t install a Meridio Server to install only the Meridio Database. The computer becomes a Meridio Database Server. 5. On the second Setup Type page, select Install a Meridio Database. At this point, the installer checks the configuration of your SQL Server authentication mode. If it is configured for Windows authentication, this prevents Meridio installing the database correctly, so a warning is displayed asking you if you wish to change the authentication mode now. Choose to do this. Installation cannot continue with Windows authentication Mixed Mode authentication is required. The installer also performs a language compatibility check to ensure that your regional settings are configured to support your selected language. The installer also checks your SQL Server language configuration. Chapter 4 - Meridio Server Database Only Installation 29

37 Once the server has been configured for a given language it cannot be changed unless the software is uninstalled and re-installed. A specific language version of the server will default to the same language for future releases. 6. On the next page, enter the name by which you want the Meridio system to be known. The system name may be up to 32 characters in length, and may contain alphanumeric characters, spaces and the following punctuation characters: ( ) { } [ ]. $ % ^ & * _ ~? - 7. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio\Server, or browse for a different path by clicking Browse. Use the Select Destination Path screen to specify where the installation should be located. Note that you have the option of installing the Meridio Database devices and transaction log on different drives later in the installation (see steps 13 to 14). See Appendix A, Meridio Server Folder Hierarchy, for information about where Meridio files are installed. Chapter 4 - Meridio Server Database Only Installation 30

38 8. Select whether you want to use Meridio Replication. For normal installs, select Do NOT use replication. If you wish to install a server with Meridio Replication, see Meridio Replication Administration Guide for details. 9. On the Enter Text page, enter a comment to describe the database. The comment you enter here is displayed in the Description field on the Installation tab of the Meridio Administration System Properties dialog box. If you don t enter a database comment, you are prompted to confirm this. 10. On the Select Database Size page, specify the database device size. The required database size depends on how many documents, versions, users, etc. that the system will have to store. You should enter a value no less than 30MB. A more typical database size might be 600MB for a repository of 100,000 documents. 11. On the Select Database Transaction Log Size page, specify the size for the Database Transaction Log. The default size is half the given size of the Meridio Database. You should enter a value no less than 15MB. 12. On the Select Database Collation page, select the correct collation for the Meridio database. The collation selected affects the languages that can be applied by the Meridio Language Packs. Chapter 4 - Meridio Server Database Only Installation 31

39 13. On the next page, select the drive on which the Database devices will be created. The default drive is the same as the Destination Folder selected in Step 7. Only local drives with enough available space are listed. Network drives are not listed. The Meridio Database devices may be installed on a different drive to the rest of the installation. The Devices drive will also be used to house the Backup folder, in which database dumps and content file lists are temporarily stored. 14. On the next page, select the drive on which the Database Transaction Log is created. The default drive is the same as the Destination Folder selected in Step 7. Only local drives with enough available space are listed. Network drives are not listed. The Meridio Database Transaction Log may be installed on a different drive to the rest of the installation. 15. The Meridio Server Install page displays the information that you entered in the previous steps, for confirmation. When you are satisfied that the information is correct, click Next to complete the installation. When the installation has finished, the Setup Complete screen is displayed. You can later upgrade to a Server (Content or Application) running alongside the Database. To do this, you must uninstall Meridio, but choose to leave the Meridio Database behind when this option is offered to you. Then run the Setup wizard again to install the Server. Chapter 4 - Meridio Server Database Only Installation 32

40 After Installation If you were prompted to restart your computer and have not already done so, restart it now. The log file created during the installation is called out.txt and is located in the destination folder. You should check this file to ensure that no problems occurred. Chapter 4 - Meridio Server Database Only Installation 33

41 CHAPTER 5 Meridio Server Content Server Installation This chapter describes how to perform a Content Server installation of Meridio Server, both with and without a database. See Chapter 2, Meridio Architecture, for more information about the different types of Meridio Server. Installing a Meridio Content Server With a Database Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. For a non default SQL installation, you must add the following system environment variable on the machine on which you want to install Meridio Server: MERIDIO_SQL_SERVER_INSTANCE Set the value to the name of the SQL Server instance on which you want the Meridio Database (DMSDB) to be installed, in the format Server\Instance. For a non default SQL installation on a 64-bit server, the ODBC data source must be configured using the 32-bit version of the ODBC Data Source Administrator. To install a Meridio Content Server with a database: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. If the Meridio Server installer reports that Setup has detected a previous installation on your machine that cannot be upgraded directly to 5.1. and you are sure that you are trying to upgrade a 3.0, 3.0 SR-1, 3.0 SR-2, 3.0 SR-3, 3.1, 3.2, 3.3, 3.3 SR-1, 3.3 SR-2, 4.0, 4.1, 4.1 SR-1, 4.2, 4.2 SR-1, 4.2 SR-2, 4.3, 4.3 SR-1, 4.4, 4.4 SR-1, 4.4 SR-2, 5.0 or 5.0 SR-1 release, then support@meridio.com with details of the following registry key version value: HKEY_LOCAL_MACHINE/SOFTWARE/Meridio Ltd/Meridio Server. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. Chapter 5 - Meridio Server Content Server Installation 34

42 4. On the first Setup Type page, select Meridio Content Server (default) to install all the Meridio services. 5. On the second Setup Type page, select Install a Meridio Database. At this point, the installer checks the configuration of your SQL Server authentication mode. If it is configured for Windows authentication, this prevents Meridio installing the database correctly, so a warning is displayed asking you if you wish to change the authentication mode now. Choose to do this. Installation cannot continue with Windows authentication Mixed Mode authentication is required. The installer also performs a language compatibility check to ensure that your regional settings are configured to support your selected language. The installer also checks your SQL Server language configuration. Chapter 5 - Meridio Server Content Server Installation 35

43 Once the server has been configured for a given language it cannot be changed unless the software is uninstalled and re-installed. A specific language version of the server will default to the same language for future releases. 6. On the next page, enter the name by which you want the Meridio system to be known. The system name may be up to 32 characters in length, and may contain alphanumeric characters, spaces and the following punctuation characters: ( ) { } [ ]. $ % ^ & * _ ~? - 7. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. Note that you have the option of installing the Meridio Database devices and transaction log on different drives later in the installation (see steps 14 to 15). See Appendix A, Meridio Server Folder Hierarchy, for information about where Meridio files are installed. Chapter 5 - Meridio Server Content Server Installation 36

44 8. Select whether you want to use Meridio Replication. For normal installs, select Do NOT use replication. If you wish to install a server with Meridio Replication, see Meridio Replication Administration Guide for details. 9. On the next page, supply the name of the Windows domain that you wish the services to use. Your current domain is the default. You must also enter the Windows username and password to be used when starting the Meridio services. The username defaults to the username under which you have logged in. If you enter a different username, ensure that the user has Windows Administrator privileges. The Meridio services need to use a valid Windows administrator s account. Only Meridio services should use this account. See Domain Users Configuration on page 20. The account should also have the Logon as a Service privilege. If the account does not have the privileges, the Meridio services fail to start and error messages are logged. However, you can solve the problem by double-clicking any one of the Meridio services in the Services dialog box of the Windows Control Panel (in the Administrative Tools), and re-entering the username and password. The MeridioCentera service is an exception to this; it is configured with the Local System account. Chapter 5 - Meridio Server Content Server Installation 37

45 For use with unified login, a new Meridio user is created in the database with a username of the Windows account name, and a real name of Meridio Server Account. The password for the user is encrypted, but can be changed in Meridio Administration. The user is added to the Admin group by default. 10. On the Enter Text page, enter a comment to describe the database. The comment you enter here is displayed in the Description field on the Installation tab of the Meridio Administration System Properties dialog box. If you don t enter a database comment, you are prompted to confirm this. 11. On the Select Database Size page, specify the database device size. The required database size depends on how many documents, versions, users, etc. that the system will have to store. You should enter a value no less than 30MB. A more typical database size might be 600MB for a repository of 100,000 documents. 12. On the Select Database Transaction Log Size page, specify the size for the Database Transaction Log. The default size is half the given size of the Meridio Database. You should enter a value no less than 15MB. 13. On the Select Database Collation page, select the correct collation for the Meridio database. The collation selected affects the languages that can be applied by the Meridio Language Packs. Chapter 5 - Meridio Server Content Server Installation 38

46 14. On the next page, select the drive on which the Database devices will be created. The default drive is the same as the Destination Folder selected in Step 7. Only local drives with enough available space are listed. Network drives are not listed. The Meridio Database devices may be installed on a different drive to the rest of the installation. The Devices drive will also be used to house the Backup folder, in which database dumps and content file lists are temporarily stored. 15. On the next page, select the drive on which the Database Transaction Log is created. The default drive is the same as the Destination Folder selected in Step 7. Only local drives with enough available space are listed. Network drives are not listed. The Meridio Database Transaction Log may be installed on a different drive to the rest of the installation. 16. The Meridio Server Install page displays the information that you entered in the previous steps, for confirmation. When you are satisfied that the information is correct, click Next to complete the installation. When the installation has finished, the Setup Complete screen is displayed. You need to restart your computer after installing Meridio Server. You have the option of restarting it immediately or leaving it to a more convenient time. After Installation If you were prompted to restart your computer and have not already done so, restart it now this starts the Meridio services and completes the creation of the audit log shared directories (see Meridio Auditing Administration Guide). Run IdolConfigUtility.exe (located by default in C:\Meridio\Server\bin) once all Meridio servers have been installed. This utility only needs to be run once to update all servers, and can be run on any server. The log file created during the installation is called out.txt and is located in the destination folder. You should check this file to ensure that no problems occurred. Chapter 5 - Meridio Server Content Server Installation 39

47 The Meridio Server hierarchy of folders is described in Appendix A, Meridio Server Folder Hierarchy. See this appendix to ensure that the hierarchy has been installed correctly on your machine, and also to gain an understanding of the purpose of each folder. Eight services will have been added to the Windows Service Control Manager. To view them select the Services icon in the Windows Control Panel. All the services, except MeridioCentera, start automatically when the server machine is rebooted. The services are: Meridio Scheduler Meridio Server Meridio Storage Agent MeridioCentera (starts when required by a Centera system using Meridio) IDOL content search services: Meridio AutonomyIDOLServer Meridio DAH Meridio DIH Meridio OmniGroupServer A program group called Meridio Server is present in the Start menu, from which the Server Utility program icons (Archive, Backup, Restore, RPC Tool, Event Hooks and Keyword Importer) are accessible. Installing a Meridio Content Server Without a Database Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. To install a Meridio Content Server without a database: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. If the Meridio Server installer reports that Setup has detected a previous installation on your machine that cannot be upgraded directly to 5.1. and you are sure that you are trying to upgrade a 3.0, 3.0 SR-1, 3.0 SR-2, 3.0 SR-3, 3.1, 3.2, 3.3, 3.3 SR-1, 3.3 SR-2, 4.0, 4.1, 4.1 SR-1, 4.2, 4.2 SR-1, 4.2 SR-2, 4.3, 4.3 SR-1, 4.4, 4.4 SR-1, 4.4 SR-2, 5.0 or 5.0 SR-1 release, then support@meridio.com with details of the following registry key version value: HKEY_LOCAL_MACHINE/SOFTWARE/Meridio Ltd/Meridio Server. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. Chapter 5 - Meridio Server Content Server Installation 40

48 4. On the first Setup Type page, select Meridio Content Server (default) to install all the Meridio services. 5. On the second Setup Type page, select Don t Install a Meridio Database. The installer performs a language compatibility check to ensure that your regional settings are configured to support your selected language. Once the server has been configured for a given language it cannot be changed unless the software is uninstalled and re-installed. A specific language version of the server will default to the same language for future releases. Chapter 5 - Meridio Server Content Server Installation 41

49 6. On the next page, enter the name of the SQL Server on which the Meridio Database resides. 7. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. See Appendix A, Meridio Server Folder Hierarchy, for information about where Meridio files are installed. 8. Select whether you want to use Meridio Replication. For normal installs, select Do NOT use replication. If you wish to install a server with Meridio Replication, see Meridio Replication Administration Guide for details. Chapter 5 - Meridio Server Content Server Installation 42

50 9. On the next page, supply the name of the Windows domain that you wish the services to use. Your current domain is the default. You must also enter the Windows username and password to be used when starting the Meridio services. The username defaults to the username under which you have logged in. If you enter a different username, ensure that the user has Windows Administrator privileges. The Meridio services need to use a valid Windows administrator s account. Only Meridio services should use this account. See Domain Users Configuration on page 20. The account should also have the Logon as a Service privilege. If the account does not have the privileges, the Meridio services fail to start and error messages are logged. However, you can solve the problem by double-clicking any one of the Meridio services in the Services dialog box of the Windows Control Panel (in the Administrative Tools), and re-entering the username and password. The MeridioCentera service is an exception to this; it is configured with the Local System account. For use with unified login, a new Meridio user is created in the database with a username of the Windows account name, and a real name of Meridio Server Account. The password for the user is encrypted, but can be changed in Meridio Administration. The user is added to the Admin group by default. 10. The Meridio Server Install page displays the information that you entered in the previous steps, for confirmation. When you are satisfied that the information is correct, click Next to complete the installation. When the installation has finished, the Setup Complete screen is displayed. You need to restart your computer after installing Meridio Server. You have the option of restarting it immediately or leaving it to a more convenient time. Chapter 5 - Meridio Server Content Server Installation 43

51 After Installation If you were prompted to restart your computer and have not already done so, restart it now this starts the Meridio services and completes the creation of the audit log shared directories (see Meridio Auditing Administration Guide). Run IdolConfigUtility.exe (located by default in C:\Meridio\Server\bin) once all Meridio servers have been installed. This utility only needs to be run once to update all servers, and can be run on any server. The log file created during the installation is called out.txt and is located in the destination folder. You should check this file to ensure that no problems occurred. The Meridio Server hierarchy of folders is described in Appendix A, Meridio Server Folder Hierarchy. See this appendix to ensure that the hierarchy has been installed correctly on your machine, and also to gain an understanding of the purpose of each folder. Eight services will have been added to the Windows Service Control Manager. To view them select the Services icon in the Windows Control Panel. All the services, except MeridioCentera, start automatically when the server machine is rebooted. The services are: Meridio Scheduler Meridio Server Meridio Storage Agent MeridioCentera (starts when required by a Centera system using Meridio) IDOL content search services: Meridio AutonomyIDOLServer Meridio DAH Meridio DIH Meridio OmniGroupServer If Meridio Server has been installed on the same machine as the Meridio Database but there is no default SQL Server instance, the following registry entry must be edited to remove mssqlserver from the value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Meridio Server\DependOnService A program group called Meridio Server is present in the Start menu, from which the Server Utility program icons (Archive, Backup, Restore, RPC Tool, Event Hooks and Keyword Importer) are accessible. Chapter 5 - Meridio Server Content Server Installation 44

52 CHAPTER 6 Meridio Server Application Server Installation This chapter describes how to perform an Application Server installation of Meridio Server, both with and without a database. Installing a Meridio Application Server With a Database Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. For a non default SQL installation, you must add the following system environment variable on the machine on which you want to install Meridio Server: MERIDIO_SQL_SERVER_INSTANCE Set the value to the name of the SQL Server instance on which you want the Meridio Database (DMSDB) to be installed, in the format Server\Instance. For a non default SQL installation on a 64-bit server, the ODBC data source must be configured using the 32-bit version of the ODBC Data Source Administrator. To install a Meridio Application Server with a database: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. If the Meridio Server installer reports that Setup has detected a previous installation on your machine that cannot be upgraded directly to 5.1. and you are sure that you are trying to upgrade a 3.0, 3.0 SR-1, 3.0 SR-2, 3.0 SR-3, 3.1, 3.2, 3.3, 3.3 SR-1, 3.3 SR-2, 4.0, 4.1, 4.1 SR-1, 4.2, 4.2 SR-1, 4.2 SR-2, 4.3, 4.3 SR-1, 4.4, 4.4 SR-1, 4.4 SR-2, 5.0 or 5.0 SR-1 release, then support@meridio.com with details of the following registry key version value: HKEY_LOCAL_MACHINE/SOFTWARE/Meridio Ltd/Meridio Server. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. Chapter 6 - Meridio Server Application Server Installation 45

53 4. On the first Setup Type page, select Meridio Application Server to install only the Meridio Server service. No document versions, renditions or indexes will be stored on this computer. 5. On the second Setup Type page, select Install a Meridio Database. The installer now checks the configuration of your SQL Server authentication mode. If it is configured for Windows authentication, this prevents Meridio installing the database correctly, so a warning is displayed asking you if you wish to change the authentication mode now. Choose to do this. Installation cannot continue with Windows authentication Mixed Mode authentication is required. The installer also performs a language compatibility check to ensure that your regional settings are configured to support your selected language. The installer also checks your SQL Server language configuration. Chapter 6 - Meridio Server Application Server Installation 46

54 Once the server has been configured for a given language it cannot be changed unless the software is uninstalled and re-installed. A specific language version of the server will default to the same language for future releases. The next page displays a warning to remind you that you must install a Content Server before attempting to start the application server. 6. On the next page, enter the name by which you want the Meridio system to be known. The system name may be up to 32 characters in length, and may contain alphanumeric characters, spaces and the following punctuation characters: ( ) { } [ ]. $ % ^ & * _ ~? - 7. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. Note that you have the option of installing the Meridio Database devices and transaction log on different drives later in the installation (see steps 13 to 15). See Appendix A, Meridio Server Folder Hierarchy, for information about where Meridio files are installed. Chapter 6 - Meridio Server Application Server Installation 47

55 8. Select whether you want to use Meridio Replication. For normal installs, select Do NOT use replication. If you wish to install a server with Meridio Replication, see Meridio Replication Administration Guide for details. 9. On the next page, supply the name of the Windows domain that you wish the services to use. Your current domain is the default. You must also enter the Windows username and password to be used when starting the Meridio services. The username defaults to the username under which you have logged in. If you enter a different username, ensure that the user has Windows Administrator privileges. The Meridio services need to use a valid Windows administrator s account. Only Meridio services should use this account. See Domain Users Configuration on page 20. The account should also have the Logon as a Service privilege. If the account does not have the privileges, the Meridio services fail to start and error messages are logged. However, you can solve the problem by double-clicking any one of the Meridio services in the Services dialog box of the Windows Control Panel (in the Administrative Tools), and re-entering the username and password. The MeridioCentera service is an exception to this; it is configured with the Local System account. Chapter 6 - Meridio Server Application Server Installation 48

56 10. For use with unified login, a new Meridio user is created in the database with a username of the Windows account name, and a real name of Meridio Server Account. The password for the user is encrypted, but can be changed in Meridio Administration. The user is added to the Admin group by default. 11. On the Enter Text page, enter a comment to describe the database. The comment you enter here is displayed in the Description field on the Installation tab of the Meridio Administration System Properties dialog box. If you don t enter a database comment, you are prompted to confirm this. 12. On the Select Database Size page, specify the database device size. The required database size depends on how many documents, versions, users, etc. that the system will have to store. You should enter a value no less than 30MB. A more typical database size might be 600MB for a repository of 100,000 documents. 13. On the Select Database Transaction Log Size page, specify the size for the Database Transaction Log. The default size is half the given size of the Meridio Database. You should enter a value no less than 15MB. 14. On the Select Database Collation page, select the correct collation for the Meridio database. The collation selected affects the languages that can be applied by the Meridio Language Packs. Chapter 6 - Meridio Server Application Server Installation 49

57 15. On the next page, select the drive on which the Database devices will be created. The default drive is the same as the Destination Folder selected in Step 7. Only local drives with enough available space are listed. Network drives are not listed. The Meridio Database devices may be installed on a different drive to the rest of the installation. The Devices drive will also be used to house the Backup folder, in which database dumps and content file lists are temporarily stored. 16. On the next page, select the drive on which the Database Transaction Log is created. The default drive is the same as the Destination Folder selected in Step 7. Only local drives with enough available space are listed. Network drives are not listed. The Meridio Database Transaction Log may be installed on a different drive to the rest of the installation. 17. The Meridio Server Install page displays the information that you entered in the previous steps, for confirmation. When you are satisfied that the information is correct, click Next to complete the installation. 18. When the installation has finished, the Setup Complete screen is displayed. After Installation If you were prompted to restart your computer and have not already done so, restart it now this starts the Meridio services and completes the creation of the audit log shared directories (see Meridio Auditing Administration Guide). Run IdolConfigUtility.exe (located by default in C:\Meridio\Server\bin) once all Meridio servers have been installed. This utility only needs to be run once to update all servers, and can be run on any server. The log file created during the installation is called out.txt and is located in the destination folder. You should check this file to ensure that no problems occurred. The Meridio Server hierarchy of folders is described in Appendix A, Meridio Server Folder Hierarchy. See this appendix to ensure that the hierarchy has been installed Chapter 6 - Meridio Server Application Server Installation 50

58 correctly on your machine, and also to gain an understanding of the purpose of each folder. The Meridio Server and MeridioCentera services will have been added to the Windows Service Control Manager. To view them, double-click the Services icon in the Windows Control Panel. If Meridio Server has been installed on the same machine as the Meridio Database but there is no default SQL Server instance, the following registry entry must be edited to remove mssqlserver from the value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Meridio Server\DependOnService Installing a Meridio Application Server Without a Database Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. To install a Meridio Application Server without a database: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. If the Meridio Server installer reports that Setup has detected a previous installation on your machine that cannot be upgraded directly to 5.1. and you are sure that you are trying to upgrade a 3.0, 3.0 SR-1, 3.0 SR-2, 3.0 SR-3, 3.1, 3.2, 3.3, 3.3 SR-1, 3.3 SR-2, 4.0, 4.1, 4.1 SR-1, 4.2, 4.2 SR-1, 4.2 SR-2, 4.3, 4.3 SR-1, 4.4, 4.4 SR-1, 4.4 SR-2, 5.0 or 5.0 SR-1 release, then support@meridio.com with details of the following registry key version value: HKEY_LOCAL_MACHINE/SOFTWARE/Meridio Ltd/Meridio Server. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. Chapter 6 - Meridio Server Application Server Installation 51

59 4. On the first Setup Type page, select Meridio Application Server to install only the Meridio Server service. No document versions, renditions or indexes will be stored on this computer. 5. On the second Setup Type page, select Don t Install a Meridio Database. The installer performs a language compatibility check to ensure that your regional settings are configured to support your selected language. Once the server has been configured for a given language it cannot be changed unless the software is uninstalled and re-installed. A specific language version of the server will default to the same language for future releases. Chapter 6 - Meridio Server Application Server Installation 52

60 6. On the next page, enter the name of the SQL Server on which the Meridio Database resides. 7. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. See Appendix A, Meridio Server Folder Hierarchy, for information about where Meridio files are installed. 8. On the next page, supply the name of the Windows domain that you wish the services to use. Your current domain is the default. You must also enter the Windows username and password to be used when starting the Meridio services. The username defaults to the username under which you have logged in. If you enter a different username, ensure that the user has Windows Administrator privileges. The Meridio services need to use a valid Windows administrator s account. Only Meridio services should use this account. See Domain Users Configuration on page 20. The account should also have the Logon as a Service privilege. If the account does not have the privileges, the Meridio services fail to start and error messages are logged. However, you can solve the problem by double-clicking any one of the Meridio services in the Services dialog box of the Windows Control Panel (in the Administrative Tools), and re-entering the username and password. The MeridioCentera service is an exception to this; it is configured with the Local System account. Chapter 6 - Meridio Server Application Server Installation 53

61 9. For use with unified login, a new Meridio user is created in the database with a username of the Windows account name, and a real name of Meridio Server Account. The password for the user is encrypted, but can be changed in Meridio Administration. The user is added to the Admin group by default. 10. The Meridio Server Install page displays the information that you entered in the previous steps, for confirmation. When you are satisfied that the information is correct, click Next to complete the installation. 11. When the installation has finished, the Setup Complete screen is displayed. You need to restart your computer after installing Meridio Server. You have the option of restarting it immediately or leaving it to a more convenient time. After Installation If you were prompted to restart your computer and have not already done so, restart it now this starts the Meridio services and completes the creation of the audit log shared directories (see Meridio Auditing Administration Guide). Run IdolConfigUtility.exe (located by default in C:\Meridio\Server\bin) once all Meridio servers have been installed. This utility only needs to be run once to update all servers, and can be run on any server. The log file created during the installation is called out.txt and is located in the destination folder. You should check this file to ensure that no problems occurred. The Meridio Server hierarchy of folders is described in Appendix A, Meridio Server Folder Hierarchy. See this appendix to ensure that the hierarchy has been installed correctly on your machine, and also to gain an understanding of the purpose of each folder. The Meridio Server and MeridioCentera services will have been added to the Windows Service Control Manager. To view them, double-click the Services icon in the Windows Control Panel. Chapter 6 - Meridio Server Application Server Installation 54

62 CHAPTER 7 Meridio Records Management Database Upgrade This chapter describes how to upgrade a Meridio system for records management functionality. Although it is possible to uninstall the Meridio Records Management Database Upgrade, using Add/Remove Programs, this has no effect on the Meridio database. Meridio Records Management Database Upgrade can only be installed on a server with an existing Meridio Database. Installation Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. To install Meridio Records Management Database Upgrade: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. 4. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. 5. On the Web Services page, enter or select the name of the target Meridio Web Services installation (or web farm) that will be used. 6. The summary page displays the information that you entered in the previous steps, for confirmation. It also shows both the amount of disk space required for the various parts of the installation, and the amount of space available in each case. You cannot continue unless the space requirements are met. However, if there is not enough space available on the current drive for the installation to take place, or you notice that some of the details entered are incorrect, you can click Back to return to the previous pages in the wizard where you can browse to select a destination path that has more free space or change other information. Chapter 7 - Meridio Records Management Database Upgrade 55

63 7. When you are satisfied that the information is correct, click Next to complete the installation. All application files are copied to the installation directory. A progress bar and displayed messages indicate the progress of the installation. 8. Once the files have been copied, a Thank You page is displayed. Click Finish to exit the wizard. If you do not wish to view the README file, then clear the check box. 9. Restart the Meridio services for all Meridio servers which use the database that has been upgraded; also restart IIS. Hiding Parts in Meridio Records Management An SQL script can be run to hide parts in Meridio clients such as Meridio for Web Users and Meridio for Microsoft SharePoint. This action is irreversible once parts have been hidden with this script, they cannot be unhidden. The script, ActivateHideParts.sql, is located in the RMDatabase folder, in the Meridio installation folder on the Meridio Server machine, and must be run with either SQL Server Query Analyzer (SQL Server 2000) or SQL Server Management Studio (SQL Server 2005). Restart IIS after running ActivateHideparts.sql. If parts are hidden, new physical and hybrid parts cannot be added to the Meridio system. Chapter 7 - Meridio Records Management Database Upgrade 56

64 CHAPTER 8 Meridio Administration Installation This chapter describes how to install the Meridio Administration application, used to manage various aspects of the Meridio system, such as groups and users. See Meridio for System Administrators for details of using Meridio Administration. Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. To install Meridio Administration: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. 4. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. 5. The Installation Requirements page displays the information that you entered in the previous steps, for confirmation. It also shows both the amount of disk space required for the various parts of the installation, and the amount of space available in each case. You cannot continue unless the space requirements are met. However, if there is not enough space available on the current drive for the installation to take place, or you notice that some of the details entered are incorrect, you can click Back to return to the previous pages in the wizard where you can browse to select a destination path that has more free space or change other information. 6. When you are satisfied that the information is correct, click Next to complete the installation. All application files are copied to the installation directory. A progress bar and displayed messages indicate the progress of the installation. 7. Once the files have been copied, a Thank You page is displayed. Click Finish to exit the wizard. If you do not wish to view the README file, then clear the check box. A Meridio program group is created in the Windows Start menu. You can then launch the application by expanding Meridio and clicking Administration. Chapter 8 - Meridio Administration Installation 57

65 CHAPTER 9 Meridio SOAP Installation It is recommended that any machine on which Meridio SOAP is to be installed should have at least 256MB of RAM. Meridio SOAP must be installed on the same machine as Meridio Web Services. If Meridio for Web Users is installed separately to Meridio Web Services and is configured to use the web services in-process (see Chapter 17, Meridio for Web Users Configuration Settings,), then Meridio SOAP must be also be installed on the same machine as Meridio for Web Users. If installing Meridio SOAP on a 64-bit # Windows 2003 server, IIS must be set to 32-bit and the 32-bit version of ASP.NET must be registered and enabled. Before Installation The following section describes any configuration that must be done before installing Meridio SOAP. Shared Download Location The Meridio SOAP API allows SOAP clients to request references to copies of Meridio files. In response to these requests, the Meridio SOAP server copies the Meridio files to a given location, which must be specified during the Meridio SOAP installation process. You must create this shared folder before starting the Meridio SOAP installation. The folder does not have to be on the machine on which you will be installing Meridio SOAP. You must also ensure that the permissions on the folder allow SOAP clients to read from the folder and allow Meridio SOAP servers to write to and read from the folder. Care must be taken when setting these permissions, so that access to the files in the shared folder is restricted as much as possible. Web Service Extensions The status of the following web service extensions must be set to Allow in IIS Manager: Active Server Pages ASP.NET v Installation Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. # The 64-bit platform refers to the x64 edition of Windows Server 2003 in WOW64 emulation mode. Chapter 9 - Meridio SOAP Installation 58

66 To install Meridio SOAP: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. 4. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. 5. The Virtual Directory Name page is displayed, on which you need to enter the name of the virtual directory for the MeridioSOAP.asp endpoint. This virtual directory references the actual MeridioSOAP.asp file, which the installation places in the Meridio SOAP installation folder. The resulting URL is the target endpoint for calls into the Meridio SOAP API. You can accept the default virtual directory name MeridioSOAP or enter a different name. If the default is selected, then the URL is: Chapter 9 - Meridio SOAP Installation 59

67 6. The Websites page is displayed, on which you need to select the web site where the Meridio SOAP virtual directory specified in the previous step will be created. 7. The Meridio System page is displayed, on which you need to select the name of the Meridio system that is the target system for this installation of Meridio SOAP. If the Meridio system name has embedded spaces, it may appear with the spaces removed. In this case, select it from the list and re-enter the embedded spaces, or enter the entire Meridio system name including embedded spaces. Chapter 9 - Meridio SOAP Installation 60

68 8. The Select Download UNC Path page is displayed, on which you need to select the shared folder that will be used to store copied Meridio files for reference by SOAP clients (see Shared Download Location on page 58). Click Browse to display the Choose Folder dialog box in which you can enter or browse for the UNC name of the folder. For example, if the folder C:\SOAP\DownloadFiles is on the machine DMS1 and is shared as DownloadFiles, its UNC name is \\DMS1\DownloadFiles. 9. On the next page, enter the name of the computer on which files converted to HTML by Meridio SOAP will be placed. This may be the computer on which Meridio SOAP is being installed or a different computer. This name will be used in URLs that client applications use to access Meridio documents in HTML format, e.g. DMS1 for Intranet access or DMS1.Meridio.com for Internet access. Chapter 9 - Meridio SOAP Installation 61

69 10. The Start Copying Files page displays the information that you entered in the previous steps, for confirmation. It also shows both the amount of disk space required for the various parts of the installation, and the amount of space available in each case. You cannot continue unless the space requirements are met. However, if there is not enough space available on the current drive for the installation to take place, or you notice that some of the details entered are incorrect, you can click Back to return to the previous pages in the wizard where you can browse to select a destination path that has more free space or change other information. 11. When you are satisfied that the information is correct, click Next to complete the installation. All application files are copied to the installation directory. A progress bar and displayed messages indicate the progress of the installation. The copying process automatically stops and restarts IIS. 12. Once the files have been copied, a Thank You page is displayed. Click Finish to exit the wizard. If you do not wish to view the README file, then clear the check box. After Installation Ensure that Domain Users are granted both Read and Write access to the C:\Meridio\SOAP\MeridioSOAP\HtmlConversion folder. Any problems that occur in Meridio SOAP will be logged in the Windows Application Event Log. See Chapter 12, Monitoring Meridio, of Meridio for System Administrators for more information. The Meridio SOAP API Endpoint Meridio SOAP runs under IIS via an Active Server Page, MeridioSOAP.asp. The URL of this ASP is the target endpoint for Meridio SOAP API requests and is created by the Meridio SOAP installation process. Anonymous access is enabled by default for the SOAP virtual directory. This must be kept enabled for the Meridio SOAP Server to function unless using Unified Login see Chapter 15, Unified and Explicit Login. Anonymous access is configured on the Directory Security tab of the Meridio SOAP virtual directory Properties dialog box. In an Active Directory domain, it is recommended that the account used for anonymous access should be changed from the default IUSR_computername account to a domain account. Security Issues The Meridio SOAP API is based on the HTTP protocol. As this is a clear-text protocol, over which information such as Meridio passwords and potentially sensitive Meridio Chapter 9 - Meridio SOAP Installation 62

70 data will be transmitted, it is strongly advised that all access to the Meridio SOAP API should run over SSL (i.e. HTTPS) for secure interaction. It is important to note that the use of HTTPS is not an intrinsic part of the Meridio SOAP product but is instead an IIS configuration issue. It is therefore the responsibility of the Meridio SOAP administrator to correctly configure IIS to use SSL for access to the Meridio SOAP entry point, MeridioSOAP.asp. Consult the IIS documentation for further details on the configuration of HTTPS. Chapter 9 - Meridio SOAP Installation 63

71 CHAPTER 10 Meridio Web Services Installation This chapter describes the installation of Meridio Web Services. The Meridio for Web Users client is installed as part of the Meridio Web Services installation. If you are intending to use replication in your Meridio system, see Meridio Replication Guide for information on installing Meridio Web Services with replication. Before Installation Before installing Meridio Web Services you must install Meridio SOAP. See Chapter 9, Meridio SOAP Installation, for further details. If installing Meridio Web Services on a 64-bit # Windows 2003 server, IIS must be set to 32-bit and the 32-bit version of ASP.NET must be registered and enabled. Web Service Extensions The status of the following web service extensions must be set to Allow in IIS Manager: Active Server Pages ASP.NET v Installation Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. The Meridio Web Services installer must be run from a location which also contains the Meridio Link Manager installer this is always the case if run from the Meridio installation CD. To install Meridio Web Services: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. # The 64-bit platform refers to the x64 edition of Windows Server 2003 in WOW64 emulation mode. Chapter 10 - Meridio Web Services Installation 64

72 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. 4. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. 5. The Websites page is displayed, on which you need to select the web site where Meridio Web Services will be installed. 6. On the Database Access page, enter the name of the database server on which the target Meridio database is installed, and the username and password of a SQL Server user with the System Administrators role for the DMSDB database. If the Meridio database is installed on a named SQL instance, you must append the instance name to the database server name, in the format Server\Instance. Chapter 10 - Meridio Web Services Installation 65

73 7. On the next page, you are prompted whether you want to use Meridio Replication. For normal installs, select No. If you wish to install Meridio Web Services for a replication environment, see Meridio Replication Administration Guide for details. 8. On the SMTP Server page, enter the name of a machine that can be used as an SMTP server to send s. 9. The next page presents a summary of the options you have selected in the wizard. If you click Next, the Meridio Web Services files are copied to the installation directories. 10. After the files have been copied, a Thank You page is displayed. Click Finish to exit the wizard. If you do not wish to view the README file, then clear the check box. Chapter 10 - Meridio Web Services Installation 66

74 After Installation For users to be able to connect to Meridio for Web Users at you must use IIS Admin to add default.aspx to the list of default documents for the Meridio virtual directory. See Chapter 16, Meridio Web Services Configuration Settings, for details of configuration options for Meridio Web Services. See Chapter 17, Meridio for Web Users Configuration Settings, for details of configuration options for Meridio for Web Users. Chapter 10 - Meridio Web Services Installation 67

75 CHAPTER 11 Meridio for Web Users Installation This chapter describes a stand-alone installation of Meridio for Web Users. Before Installation Meridio Web Services must be installed on a different machine before Meridio for Web Users is installed Meridio for Web Users cannot be installed on a machine on which Meridio Web Services is already installed. Before installing Meridio Web Services you must install Meridio SOAP. See Chapter 9, Meridio SOAP Installation, for further details. If installing Meridio Web Services on a 64-bit # Windows 2003 server, IIS must be set to 32-bit and the 32-bit version of ASP.NET must be registered and enabled. Web Service Extensions The status of the following web service extensions must be set to Allow in IIS Manager: Active Server Pages ASP.NET v Installation Before beginning the installation process you should close all other applications. You must be a member of the Windows Administrators group for the computer on which you are installing. This is necessary to create the Meridio registry entries. When you are ready to begin, double-click setup.exe to launch the installation wizard. The Meridio for Web Users installer must be run from a location which also contains the Meridio Link Manager installer this is always the case if run from the Meridio installation CD. To install Meridio for Web Users: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. # The 64-bit platform refers to the x64 edition of Windows Server 2003 in WOW64 emulation mode. Chapter 11 - Meridio for Web Users Installation 68

76 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. 4. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. 5. The Websites page is displayed, on which you need to select the web site where Meridio for Web Users will be installed. 6. The Web Services page is displayed. Enter the location of the target Meridio Web Services installation (or web farm) that is used by this installation of Meridio for Web Users. Chapter 11 - Meridio for Web Users Installation 69

77 7. On the Database Access page, enter the name of the database server on which the target Meridio database is installed, and the username and password of a SQL Server user with the System Administrators role for the DMSDB database. 8. On the next page, you are prompted whether you want to use Meridio Replication. For normal installs, select Does NOT use Meridio Replication. If you wish to install Meridio for Web Users for a replication environment, see Meridio Replication Administration Guide for details. 9. On the Use Remote Content Server page, select whether you wish the Meridio Web Services to use a Meridio Remote Content Server for document content retrievals. If you selected Yes, an additional page is displayed asking for the name of the machine running the Meridio Remote Content Server. Chapter 11 - Meridio for Web Users Installation 70

78 10. The next page presents a summary of the options you have selected in the wizard. If you click Next, the Meridio Web Services files are copied to the installation directories. 11. After the files have been copied, a Thank You page is displayed. Click Finish to exit the wizard. If you do not wish to view the README file, then deselect the check box. After Installation For users to be able to connect to Meridio for Web Users at you must use IIS Admin to add default.aspx to the list of default documents for the Meridio virtual directory. See Chapter 17, Meridio for Web Users Configuration Settings, for details of configuration options for Meridio for Web Users. Chapter 11 - Meridio for Web Users Installation 71

79 CHAPTER 12 Meridio for Microsoft SharePoint 2003 Installation The installation process consists of three phases: 1. Making pre-installation checks of software and network requirements (see page 72). 2. Installing Meridio for Microsoft SharePoint software using the Setup wizard provided (see page 73). 3. Carrying out post-installation procedures, to ensure that the software is ready for use, described in Chapter 18, Meridio for Microsoft SharePoint Configuration Settings. Before Installation The following software and network requirements must be met before Meridio for Microsoft SharePoint can be installed. Software Requirements Meridio for Microsoft SharePoint can only be installed on a Windows 2003 Server (Service Pack 1 or 2) machine that has either: Microsoft SharePoint Portal Server (Service Pack 1 or 2) Microsoft Windows SharePoint Services 2.0 (Service Pack 1 or 2) You must have Windows 2003 Administrator privileges on your computer and be an Administrator within Microsoft SharePoint Portal Server before attempting to install Meridio for Microsoft SharePoint. If you choose to install the Meridio search protocol handler, then Meridio for Microsoft SharePoint must be installed on an NTFS drive. If installing Meridio for Microsoft SharePoint on a 64-bit # Windows 2003 server, IIS must be set to 32-bit and the 32-bit version of ASP.NET must be registered and enabled. Network Requirements The machine on which Meridio for Microsoft SharePoint is being installed must be able to access the target Meridio system. The target system must have the Meridio Records Management Database installed and must include a machine on which the Meridio Web Services have been installed. If the Meridio search protocol handler is to be installed, the machine must be able to ping a machine on which a Meridio Server is installed. # The 64-bit platform refers to the x64 edition of Windows Server 2003 in WOW64 emulation mode. Chapter 12 - Meridio for Microsoft SharePoint 2003 Installation 72

80 All Meridio users and groups (including, for example, End Users) must also exist in the Windows domain (i.e. in Active Directory) in order for the search protocol handler to function correctly. Installation For Microsoft SharePoint 2003, the Meridio for Microsoft SharePoint files and the SharePoint Protocol Search Handler are installed as part of the same process. Before beginning the installation process you should close all other applications. When you are ready to begin, double-click setup.exe to launch the installation wizard. The Meridio for Microsoft SharePoint 2003 installer must be run from a location which also contains the Meridio Link Manager installer this is always the case if run from the Meridio installation CD. To install Meridio for Microsoft SharePoint 2003: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. 4. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. Note that if the Meridio for Microsoft SharePoint search protocol handler is to be installed, the drive chosen must be an NTFS drive. 5. If Meridio for Microsoft SharePoint is installed on a Microsoft SharePoint Portal Server, on the next page, specify whether Meridio for SharePoint and/or the Meridio for SharePoint search protocol handler are to be installed. Select the items to be installed. If you have selected the installation of the Meridio for SharePoint client files, two more screens are displayed: i. If Meridio Web Services is installed on the local machine, the Access to Web Services page is displayed. Select how you wish to access Meridio Web Services: by accessing local Meridio Web Services in-process by accessing local or remote Meridio Web Services via HTTP If you selected Access local Meridio Web Services in-process, clicking Next displays the Meridio SOAP Server page. Select the name of the Meridio SOAP server to use, and enter a name for the Meridio SOAP virtual directory (the default is MeridioSOAP). Clicking Next then displays the Database Access page. Chapter 12 - Meridio for Microsoft SharePoint 2003 Installation 73

81 Enter the name of the Meridio Database server, and the username and password for a database account with the ability to create a database. If Meridio Web Services is not installed on the local machine, or you selected Access local or remote Meridio Web Services via HTTP, the Web Services page is displayed. Enter the location of the target Meridio Web Services installation (or web farm) that is used by this installation of Meridio for Web Users. ii. On the Use Remote Content Server page, select whether you wish the Meridio for Web Users application to use a Meridio Remote Content Server for document content retrievals. If you selected Yes, an additional page is displayed asking for the name of the machine running the Meridio Remote Content Server. A list of web sites on the machine is displayed. Select those sites which are to be updated as part of the installation of the client software. iii. On the Determine Meridio Replication Status page, select whether the system is part of a replication group. 6. If you have selected the installation of the Meridio for SharePoint search protocol handler, three more screens are displayed: i. Enter the name of the Meridio system whose content is to be searched. ii. Enter the account details of a Meridio user to be used to retrieve records from the Meridio system for indexing by SharePoint. This user must have Read access to all of the documents, fileplans and records that you wish to index. This means that you must assign protective markings to the user if you use protective markings on the fileplan structure and wish the items within the fileplan to be indexed. Enter the name of the default domain to be used for searches. When mapping Meridio user names to Windows user names, the default domain is the first domain in which Windows accounts are looked for. All Meridio users and groups (including, for example, End Users) must also exist in the Windows domain (i.e. in Active Directory) in order for the search protocol handler to function correctly. 7. On the next page, select the name of any web sites on which Microsoft SharePoint is installed and is to be updated with Meridio for Microsoft SharePoint. 8. The Start Copying Files page displays the information that you entered in the previous steps, for confirmation. It also shows both the amount of disk space required for the various parts of the installation, and the amount of space available in each case. You cannot continue unless the space requirements are met. However, if there is not enough space available on the current drive for the installation to take place, or you notice that some of the details entered are incorrect, you can click Back to return to the previous pages in the wizard where you can browse to select a destination path that has more free space or change other information. 9. When you are satisfied that the information is correct, click Next to complete the installation. All application files are copied to the installation directory. A progress bar and displayed messages indicate the progress of the installation. Chapter 12 - Meridio for Microsoft SharePoint 2003 Installation 74

82 10. Once the files have been copied, a Thank You page is displayed. Click Finish to exit the wizard. After Installation After the installation is complete, restart IIS. See Configuring Meridio for Microsoft SharePoint on page 100 for details of configuring unified login, if required. See Chapter 18, Meridio for Microsoft SharePoint Configuration Settings, for further configuration details. Configuring Meridio Document Store Searching To enable searching across the Meridio document store, a Meridio content source must be configured within SharePoint Portal Server. This is used to create an index of information stored within the Meridio document store. Once SharePoint Portal Server includes this content in the index, it is then available for users to search for and view on the portal site. Users can only see objects in the search results if the Meridio account to which their Windows account corresponds has the relevant permissions. To configure a Meridio content source in Microsoft SharePoint: 1. On the main portal site, click Site Settings. 2. On the Site Settings dialog box, in the Search Settings and Indexed Content section, click Configure search and indexing. 3. On the Configure Search and Indexing page, in the Other Content Sources section, click Add content source. 4. On the Add Content Source page, do the following: i. Select Exchange Server public folder. ii. Click Next. 5. On the Add Content Source: Exchange Server public folder page, in the Address and Description section, do the following, with MERIDIOSYSTEM replaced by the name of the Meridio system: i. Enter meridio://meridiosystem/root in the Address field. ii. Enter MERIDIO-MERIDIOSYSTEM in the Description field. 6. In the Crawl Configuration section, leave the default radio buttons selected. 7. Click Finish to configure the Meridio content source. 8. On the Create Exchange Server public folder Content Source page, click OK. To create a server name mapping: As administrator, you must also create a server mapping name to override how Microsoft SharePoint Portal Server displays search results or how users access content after you create the Meridio content source. Chapter 12 - Meridio for Microsoft SharePoint 2003 Installation 75

83 1. On the main portal site, click Site Settings. 2. On the Site Settings page, in the Search Settings and Indexed Content section, click Configure search and indexing. 3. On the Configure Search and Indexing page, in the General Content Settings and Indexing Status section, click the link opposite Server name mappings: 4. On the Map Server Names page, click the New Mapping toolbar button. 5. On the Add Server Name Mapping page, in the Server Names section, do the following, with MERIDIOSYSTEM replaced by the name of the Meridio system and SPSERVER replaced by the name of the SharePoint Portal server: i. Enter meridio://meridiosystem in the Address in index field. ii. Enter RIDIOSYSTEM in the Address in search results field. 6. Click OK to add the new server name mapping. The screen refreshes and the Map Server Names page displays the new mapping. To run a full update of the Meridio content source: A full update of the Meridio content source must be started. 1. On the main portal site, click Site Settings. 2. On the Site Settings page, in the Search Settings and Indexed Content section, click Configure search and indexing. 3. On the Configure Search and Indexing page, in the General Content Settings and Indexing Status section, click the Full link opposite Start non portal content update. This starts a full update of the Meridio content source, the status of which can be viewed in the General Content Settings and Indexing Status section, in the Non- Portal Content column of the row corresponding to Last update status. Meridio Site Installer The Meridio Site Installer utility enables you to install Meridio for Microsoft SharePoint on additional web sites. To run the Meridio Site Installer: 1. Open the utility from Start All Programs Meridio Meridio Site Installer. The Meridio Site Installer dialog box is displayed. Chapter 12 - Meridio for Microsoft SharePoint 2003 Installation 76

84 2. Select the web sites on which you want to install Meridio for Microsoft SharePoint. 3. Click Update. The dialog box refreshes to give details of the installation process. 4. When the installation is complete, click Finish to close the dialog box. Modifying Meridio for Microsoft SharePoint You can modify an installation of Meridio for Microsoft SharePoint; for example, to use the SharePoint Search Protocol Handler. To modify a Meridio for Microsoft SharePoint 2003 installation: 1. In the Windows Control Panel, double-click Add/Remove Programs. The Add/Remove Programs Properties window is displayed. 2. Select Meridio for Microsoft SharePoint from the Install/Uninstall tab, and click Add/Remove. 3. The Uninstall wizard is displayed. Select to modify your installation of Meridio for Microsoft SharePoint. Chapter 12 - Meridio for Microsoft SharePoint 2003 Installation 77

85 4. On the next page, select if the Meridio for SharePoint client software and/or the Meridio for SharePoint search protocol handler are to be installed or uninstalled. 5. Depending on which items you select, the screens described in steps 6 and 7 of the installation procedure (see page 73) are displayed. Complete these steps to modify the installation. Chapter 12 - Meridio for Microsoft SharePoint 2003 Installation 78

86 CHAPTER 13 Meridio for Microsoft SharePoint 2007 Installation The installation process consists of four phases: 1. Making pre-installation checks of software and network requirements (see page 79). 2. Installing and configuring Meridio for Microsoft SharePoint 2007 (see page 80). 3. Installing and configuring Meridio Search Protocol Handler (see page 86). 4. Carrying out post-installation procedures, to ensure that the software is ready for use, described in Chapter 18, Meridio for Microsoft SharePoint Configuration Settings. This chapter also deals with the process of uninstalling Meridio for Microsoft SharePoint Before Installation The following software and network requirements must be met before Meridio for Microsoft SharePoint can be installed. Software Requirements Meridio for Microsoft SharePoint can only be installed on a Windows 2003 Server (Service Pack 1 or 2) machine that has either: Microsoft Office SharePoint Server 2007 (MOSS) Microsoft Windows SharePoint Services 3.0 You must have Windows 2003 Administrator privileges on your computer and be an Administrator within MOSS before attempting to install Meridio for Microsoft SharePoint. Network Requirements The machine on which Meridio for Microsoft SharePoint is being installed must be able to access the target Meridio system. The target system must have the Meridio Records Management Database installed and must include a machine on which the Meridio Web Services have been installed. If the Meridio search protocol handler is to be installed, the machine must be able to ping a machine on which a Meridio Server is installed. All Meridio users and groups (including, for example, End Users) must also exist in the Windows domain (i.e. in Active Directory) in order for the search protocol handler to function correctly. Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 79

87 Installing Meridio for Microsoft SharePoint 2007 The following checklist describes the procedure for installing, deploying and activating Meridio for Microsoft SharePoint 2007: Install the Meridio for Microsoft SharePoint 2007 files. If installing to a server farm, the installation wizard must be run on each node. Run the Meridio Configuration Wizard (see page 81). If installing to a server farm, the Meridio Configuration Wizard only needs to be run on a single node, e.g. the central administration node. You can select the following options for each web application (web site): Deploy adds the Meridio solution package to Microsoft SharePoint, and deploys it for the web application. Ignore adds the Meridio solution package to Microsoft SharePoint without deploying it for the web application. If necessary (if you selected Ignore in the Meridio Configuration Wizard), you can deploy the Meridio solution for a web application using SharePoint Central Administration (see page 85). Once the solution has been deployed for the web application, activate the web application features (see page 85). The Meridio site features are automatically activated for existing web sites in the web application. Before beginning the installation process you should close all other applications. You must have the Administrator privilege for the computer on which you are installing. (This is needed to create the Meridio registry entries.) To install Meridio for Microsoft SharePoint 2007: When you are ready to begin, double-click setup.exe to launch the installation wizard. After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. 4. The Destination Location page is displayed, on which you need to select a path for the installed files. You can accept the default path C:\Meridio, or browse for a different path by clicking Browse. 5. The Ready to Install page is displayed. Click Install to complete the installation. All application files are copied to the installation directory. A progress bar and displayed messages indicate the progress of the installation. 6. Once the files have been copied, a Completed page is displayed. Click Finish to exit the wizard. Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 80

88 If you clear the Launch the Configuration Wizard option, the installation wizard closes. You can complete the configuration later by running the Meridio Configuration wizard from Start All Programs Meridio Meridio SharePoint Website Install Wizard. Otherwise, the Meridio Configuration wizard is opened. Complete the wizard to add Meridio for Microsoft SharePoint to the appropriate web applications. Meridio Configuration Wizard The Meridio Configuration Wizard utility enables you to add and deploy the Meridio solution package to web applications. The utility can be run during installation or from Start All Programs Meridio Meridio SharePoint Website Install Wizard. The Meridio Configuration Wizard can be run at any time to add the solution, or to deploy or retract it for selected web applications. Alternatively, this can be done using SharePoint Central Administration. To add and deploy Meridio for Microsoft SharePoint to web application: After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. 2. The next page lists the pre-requisites for configuring Meridio for Microsoft SharePoint The wizard checks that these are available. 3. On the SharePoint Details page, select the SharePoint web applications to which you deploy the Meridio solution, and select Deploy from the Action drop-down list. Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 81

89 If you select Ignore, the Meridio solution package is added to the SharePoint system, and can be manually deployed after the Meridio Configuration Wizard is finished see Deploying Meridio for Microsoft SharePoint see Deploying Meridio for Microsoft SharePoint on page On the Installation Culture page, select the language for the Meridio for Microsoft SharePoint installation files. Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 82

90 5. On the Meridio Connection page, select how you wish to access Meridio Web Services: by accessing local Meridio Web Services in-process (Connect in-process) by accessing local or remote Meridio Web Services via HTTP (Do not connect inprocess) 6. On the Meridio Connection Details page, enter details of the Meridio Web Services machine as described in the following table. Option Host Name Port Number Timeout Use SSL to connect Use network login Compress content for transfer Use UNC to transfer content Description The name of the Meridio Web Services machine. The port on which Meridio Web Services are installed (the default is 80). The length of time (in seconds) after which Meridio for Microsoft SharePoint should stop trying to connect to the Meridio Web Services machine. Select to use SSL (secure socket layer) for the connection to the Meridio Web Services machine. Select to enable unified login for Meridio for Microsoft SharePoint. See Chapter 15, Unified and Explicit Login, for more information. Select to compress the content of files that are being uploaded to Meridio. Select to use UNC transfer for uploading files to Meridio. By default if this check box is cleared Meridio is configured to use Direct Internet Message Encapsulation (DIME). Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 83

91 Option UNC Upload Path Description The UNC path of the MeridioSOAP shared folder, to which files are uploaded. 7. If you selected to connect to Meridio Web Services in-process, an additional Meridio Connection Details page is displayed. Enter the name of the Meridio SOAP server to use. Enter the name of the Meridio Database server, and the username and password for a database account with the ability to create a database. Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 84

92 8. A confirmation page is displayed. Click Next to complete the installation of Meridio for Microsoft SharePoint. 9. A progress page is displayed. When the installation is complete, click Finish to exit the wizard. 10. You must now activate the web application features see Activating Meridio Web Application Features see Activating Meridio Web Application Features on page 85. After Installing Meridio for Microsoft SharePoint If necessary (if you selected Ignore during Step 3 of the Meridio Configuration Wizard), deploy the Meridio solution see Deploying Meridio for Microsoft SharePoint on page 85. Activate the Meridio web application features see Activating Meridio Web Application Features on page 85. The appropriate security must be set on the C:\Program Files\Meridio\SharePoint\Upload shared folder, so that each Meridio for Microsoft SharePoint 2007 user has full control. See Configuring Meridio for Microsoft SharePoint on page 100 for details of configuring unified login, if required. See Chapter 18, Meridio for Microsoft SharePoint Configuration Settings, for further configuration details. Deploying Meridio for Microsoft SharePoint If you have not yet deployed the Meridio solution to the required web application using the Meridio Configuration Wizard, you can deploy it from the SharePoint Central Administration web page as follows: 1. On the Operations page, click Solution Management. 2. On the Solution Management page, click the name of the Meridio solution: meridiosolution.wsp. 3. On the next page, click Deploy. The Meridio solution is deployed; you must now activate the web application features. Activating Meridio Web Application Features The Meridio web application features must be activated before Meridio can be used in Microsoft SharePoint web sites in that web application: 1. On the Application Management page in SharePoint Central Administration, click Manage web application features. 2. On the Web Application Features page, activate the following as required: Meridio Web Application Features this activates the Meridio Fileplan, Library Integration and My Workspace features on any existing web sites. Meridio site features can be further activated or deactivated at site level see Meridio Site Features for further information. Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 85

93 Meridio Records Repository Web Services this enables the use of the Send To Meridio Records Repository option for saving SharePoint documents to Meridio. If the Meridio web application features are deactivated on the Web Application Features page, the site features are also deactivated. To activate or deactivate Meridio web application features using SharePoint Central Administration, the user must have Full Control for the web application. Installing Meridio Search Protocol Handler The following checklist describes the procedure for installing and configuring the Meridio Search Protocol Handler: Install the Meridio Search Protocol Handler. Configure a Meridio content source. Server name mappings (required for indexing content for searches see page 1) cannot be created in MOSS for web sites which include port numbers. If MOSS is installed on a non-default web site, a host header is required for that web site. To install Meridio Search Protocol Handler for SharePoint 2007: When you are ready to begin, double-click Meridio Search Protocol Handler for SharePoint.msi to launch the installation wizard. After each page of the wizard, click Next to continue. 1. The first page of the wizard is a Welcome page. 2. The second page displays the Meridio software licence agreement. If you accept the terms of the agreement, click Yes to continue. 3. The Registration page is displayed. Enter the user s name, and the company name. On clicking Next, a window is displayed for confirmation. Click Yes to move to the next page of the wizard. 4. On the Destination Folder page, select a path to which the application will be installed. You can accept the default path C:\Program Files\Meridio\SharePoint\Search Protocol Handler, or browse for a different path by clicking Change. 5. On the Credentials page, enter the account details of a Meridio user to be used to retrieve records from the Meridio system for indexing by SharePoint. This user must have Read access to all of the documents, fileplans and records that you wish to index. This means that you must assign protective markings to the user if you use protective markings on the fileplan structure and wish the items within the fileplan to be indexed. Enter the name of the default domain to be used for searches. When mapping Meridio user names to Windows user names, the default domain is the first domain in which Windows accounts are looked for. Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 86

94 All Meridio users and groups (including, for example, End Users) must also exist in the Windows domain (i.e. in Active Directory) in order for the search protocol handler to function correctly. The Ready to Install page is displayed. Click Install to complete the installation. All application files are copied to the installation directory. A progress bar and displayed messages indicate the progress of the installation. 6. Once the files have been copied, a Completed page is displayed. Click Finish to exit the wizard. After Installing Meridio Search Protocol Handler To enable searching across the Meridio document store, ensure that a Shared Service Provider is created and that MOSS searching works correctly. Configuring Meridio Document Store Searching A Meridio content source must be configured. This is used to create an index of information stored within the Meridio document store. Once this content is included in the index, it is available for users to search for and view. Users can only see objects in the search results if the Meridio account to which their Windows account corresponds has the relevant permissions. To install a Meridio content source by running CSInstaller.exe: 1. In a command prompt, run C:\Program Files\Meridio\SharePoint\Search Protocol Handler\Tools\CSInstaller.exe as follows: CSInstaller ContentSourceName SPSSite MeridioSystem where: ContentSourceName is the name given to the content source Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 87

95 SPSSite is the URL of the SharePoint site MeridioSystem is the name of the Meridio system to be searched For example: CSInstaller Meridio Meridio1 2. Verify that the content source is installed by navigating to the Content Sources page for the Shared Service s Search Settings in SharePoint Central Administration. A content source can be created for each Meridio system to be searched. To create a server name mapping: As administrator, you must also create a server mapping name to override how Microsoft Office SharePoint Server displays search results or how users access content after you create the Meridio content source. The server name mapping cannot be edited once created. Server name mappings cannot be created in MOSS for web sites which include port numbers. If MOSS is installed on a non-default web site, a host header is required for that web site. 1. In SharePoint Central Administration, navigate to the Server Name Mappings page for the Shared Service s Search Settings. 2. Create a new mapping with the following details where MeridioSystem is the name of the Meridio system and SharePointServer is the name of the Microsoft Office SharePoint Server: Address in index Meridio://MeridioSystem Address in search results //MeridioSystem MeridioSystem must be the same case for each field, in other words either lower case or upper case. It must also be the same case as the MeridioSystem name specified as a content source (see To install a Meridio content source by running CSInstaller.exe on page 87). To create a crawl rule and run a full update of the Meridio content source: 1. In SharePoint Central Administration, navigate to the Content Source page for the Shared Service s Search Settings. 2. Create a new rule with the following details: Path Meridio://* Crawl Configuration Include all items in this path The other options should have the default values. 3. Restart the Office SharePoint Server Search service. 4. In SharePoint Central Administration, navigate to the Content Source page for the Shared Service s Search Settings. Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 88

96 5. From the shortcut menu for the Meridio content source, select Start Full Crawl. The progress of the update can be viewed in the crawl log and the log files created in C:\Program Files\Meridio\SharePoint\Search Protocol Handler\Checkout. Uninstalling Meridio for Microsoft SharePoint Meridio for Microsoft SharePoint can be removed from a specific web application, or can be uninstalled from the Microsoft SharePoint system. To remove Meridio for Microsoft SharePoint from a web application: 1. In SharePoint Central Administration, deactivate the Meridio web application features from the Web Application page. 2. From the Solution Management page, retract the Meridio solution, meridiosolution.wsp. To completely uninstall Meridio for Microsoft SharePoint 2007: 1. From the Solution Management page for the web application, globally retract then remove the Meridio solution, meridiosolution.wsp. By retracting the solution for the web application, the Meridio web application features are deactivated. 2. Uninstall Meridio for Microsoft SharePoint from Add/Remove Programs in the Windows Control Panel. Chapter 13 - Meridio for Microsoft SharePoint 2007 Installation 89

97 CHAPTER 14 Configuring Web Services for Database Access The following Meridio web services access the Meridio database directly: DMWS RMWS SCWS RUWS Each can be run under an end-user account in other words, the web service impersonates an end user except in the case of RMWS running out-of-process. Therefore, in order for the web service to access an authenticating resource (such as SQL Server) while impersonating an end user, it must support a mechanism for temporarily switching out of the impersonated end-user identity and into a preconfigured Windows account identity for the purpose of accessing the resource. RUWS also accesses the Meridio Transport database; see Appendix A of Meridio Replication Administration Guide for details of how to configure this. There are four possible methods of connecting a Meridio web service to the SQL Server for access to the Meridio database (DMSDB): SQL authentication with login credentials as plain text (see page 91) SQL authentication with login credentials encrypted in the registry (see page 91) Windows authentication with login credentials encrypted in the registry (see page 92) Windows authentication using the application pool account (see page 93) Aspnet_setreg.exe is used to encrypt account details into the registry. See to download aspnet_setreg.exe. In the following methods, the variables used are: DBSERVERNAME the name of the SQL Instance on which the Meridio database is installed SQLUSERNAME a SQL Server account that has access to the Meridio database SQLPASSWORD the password of the SQL Server account this must not be blank if it is to be encrypted into the registry SERVERNAME the name of the server on which Meridio Web Services is running DOMAIN\WINUSERNAME a network account that has access to the SQL Server WINPASSWORD the password of the network account If the SQL password is changed at any time, it must be updated in SQL Enterprise Manager and in all other relevant places such as the web.config files or the registry. Chapter 14 - Configuring Web Services for Database Access 90

98 Configuring SQL Authentication with Login Credentials as Plain Text If running out-of-process, ensure the following appsettings appear in the web.config file for the web service; otherwise they must appear in the config file of the client application (e.g. Meridio for Web Users): <add key= meridiodatabase value= DBSERVERNAME /> <add key= meridiodatabaseuser value= SQLUSERNAME /> <add key= meridiodatabasepassword value= SQLPASSWORD /> <!-- <add key= useregdbconnectioninfo value= false /> --> The key for useregdbconnectioninfo can either be deleted or commented out (as shown in the previous example). Configuring SQL Authentication by Encrypting Login Credentials in the Registry If running out-of-process, ensure the following appsettings appear in the web.config file of the web service; otherwise they must appear in the config file of the client application (e.g. Meridio for Web Users): <add key= meridiodatabase value= DBSERVERNAME /> <!-- <add key= meridiodatabaseuser value= SQLUSERNAME /> <add key= meridiodatabasepassword value= SQLPASSWORD /> --> <add key= useregdbconnectioninfo value= true /> The keys for meridiodatabaseuser and meridiodatabasepassword can either be deleted or commented out (as shown in the previous example). The name and password of the SQL Server account must be encrypted into registry keys using aspnet_setreg.exe. These are encrypted into: HKLM\SOFTWARE\Meridio Ltd\Meridio\Identity\ASPNET_SETREG\userName HKLM\SOFTWARE\Meridio Ltd\Meridio\Identity\ASPNET_SETREG\password Delete these registry keys if they already exist before using aspnet_setreg.exe. Use the following command to encrypt the name and password into the registry: aspnet_setreg.exe -k: SOFTWARE\Meridio Ltd\Meridio\Identity -u: SQLUSERNAME - p: SQLPASSWORD Do not use a blank SQL password! The ASP.NET worker process account is the account configured for the Application Pool in which the web service runs (by default this is NT AUTHORITY\NETWORK SERVICE). The ASP.NET worker process account (or, if running in-process, the account Chapter 14 - Configuring Web Services for Database Access 91

99 under which the client application s AppPool is running) must be given permissions to the registry key, and must not be set up as a Meridio user. See Domain Users Configuration on page 20. In the registry, right-click on the following registry key and select Permissions from the shortcut menu: HKEY_LOCAL_MACHINE\SOFTWARE\Meridio Ltd\Meridio\Identity\ASPNET_SETREG Add the ASP.NET worker process account with Read permission. Configuring Windows Authentication by Encrypting Login Credentials in the Registry If you wish to configure Windows Authentication for the Meridio database, the Windows account used to install the Meridio services and database must be the same as the account used to install SQL Server. To configure Windows Authentication for SQL Server the following steps must be completed: 1. Configure SQL Server. 2. Configure the Meridio services. 3. Configure the Meridio web services. Configuring SQL Server Configure the ODBC drivers for the SQL Server. In the ODBC Data Source Administrator, select the relevant SQL Server from the System DSN node and click Configure. On the second page of the wizard, select Windows NT authentication and proceed through the wizard until it is completed. In SQL Server Enterprise Manager, set the authentication mode for the local server to Windows only (on the Security tab of the server Properties dialog box). You will be asked if you want to restart SQL Server; click Yes. Configuring Meridio Services In SQL Server Enterprise Manager, in the Security folder for the local server, configure the account under which Meridio services are running to have public and db_owner access to the DMSDB database, and public access to the master database. Configuring Meridio Web Services If running out-of-process then ensure the following appsettings appear in the web.config file of the web service; otherwise they must appear in the config file of the client application (e.g. Meridio for Web Users): <add key= meridiodatabase value= DBSERVERNAME /> <!-- <add key= meridiodatabaseuser value= SQLUSERNAME /> <add key= meridiodatabasepassword value= SQLPASSWORD /> <add key= useregdbconnectioninfo value= false /> --> Chapter 14 - Configuring Web Services for Database Access 92

100 The keys for meridiodatabaseuser, meridiodatabasepassword and useregdbconnectioninfo can either be deleted or commented out (as shown in the previous example). If the web service is running out-of-process and is configured to impersonate callers (DMWS only), or if running in-process and the client application is configured to impersonate callers (DMWS, RMWS and SCWS), then you must also add an appsetting to the config file and encrypt account details into the registry. Uncomment the following appsetting in the same config file changed above: <add key= impersonatedbuser value= true /> The identity of the application pool under which Meridio web services are run must be an account that has public and db_owner access to the DMSDB database, and public access to the master database. See Domain Users Configuration on page 20. The name and password of a Windows account, with public and db_owner access to the DMSDB database and public access to the master database, must be encrypted into registry keys using aspnet_setreg.exe. This can be the Meridio services account or the account used for the Meridio web services application pool, if desired. These are encrypted into: HKLM\SOFTWARE\Meridio Ltd\Meridio\Identity\ASPNET_SETREG\userName HKLM\SOFTWARE\Meridio Ltd\Meridio\Identity\ASPNET_SETREG\password Delete these registry keys if they already exist before using aspnet_setreg.exe. Use the following command to encrypt the name and password into the registry: aspnet_setreg.exe -k: SOFTWARE\Meridio Ltd\Meridio\Identity -u: SQLUSERNAME - p: SQLPASSWORD Do not use a blank SQL password! It is recommended that a group representing all Meridio users is created and is given permission to the appropriate registry key. In the registry, right-click on the following registry key and select Permissions from the shortcut menu: HKEY_LOCAL_MACHINE\SOFTWARE\Meridio Ltd\Meridio\Identity\ASPNET_SETREG Add the group with Read permission. Configuring Windows Authentication Using the Application Pool Account As an alternative to explicitly setting SQL login credentials in the web.config file or encrypting them in the registry, Meridio Web Services can be configured to use the application pool account to connect to the Meridio database. The identity of the application pool under which Meridio web services are run must be an account that has public and db_owner access to the DMSDB database, and public access to the master database. See Domain Users Configuration on page 20. Chapter 14 - Configuring Web Services for Database Access 93

101 If running out-of-process, ensure the following appsettings appear in the web.config file for the web service; otherwise they must appear in the config file of the client application (e.g. Meridio for Web Users): <add key= meridiodatabase value= DBSERVERNAME /> <!-- <add key= meridiodatabaseuser value= SQLUSERNAME /> <add key= meridiodatabasepassword value= SQLPASSWORD /> <add key= useregdbconnectioninfo value= false /> --> The keys for meridiodatabaseuser, meridiodatabasepassword and useregdbconnectioninfo can either be deleted or commented out (as shown in the previous example). If the web service is running out-of-process and is configured to impersonate callers (DMWS only), or if running in-process and the client application is configured to impersonate callers (DMWS, RMWS and SCWS), then you must also add an appsetting to the config file and encrypt account details into the registry. Uncomment the following appsettings in the same config file changed above and ensure the values are true: <add key= impersonatedbuser value= true /> <add key= impersonateapppoolaccount value= true /> Chapter 14 - Configuring Web Services for Database Access 94

102 CHAPTER 15 Unified and Explicit Login This chapter details how to set up Unified Login and Explicit Login in a simple server set-up. Unified Login Unified Login is a method of gaining authenticated access to a Meridio system without the need to specify Meridio login credentials the user s network login credentials are used instead. The user is logged into the Meridio system if their network username matches a Meridio username; passwords are not required. The following diagram illustrates a possible architecture configuration for a Meridio system on which you intend to use unified login. Machine 1 Meridio database (SQL Server) Machine 2 Meridio Server Meridio SOAP Meridio Web Services Machine 3 Meridio for Web Users Machine 4 Meridio user s web browser To configure unified login successfully for this system, the steps in the following checklist must be completed: Configure the Meridio Server. If Meridio Server and Meridio SOAP are installed on different machines, configure Kerberos security for Meridio Server. Configure Meridio SOAP (see page 96). Configure Kerberos security for Meridio SOAP (see page 97). Configure Meridio Web Services (see page 97). Configure Kerberos security for Meridio Web Services (see page 97). Configure Meridio for Web Users: 1. Configure the machine on which Meridio for Web Users is installed (see page 98). 2. Configure Kerberos security for Meridio for Web Users (see page 99). 3. Configure the machine which accesses Meridio for Web Users through Internet Explorer (see page 99). Chapter 15 - Unified and Explicit Login 95

103 If relevant, configure Meridio for Microsoft SharePoint: 1. Configure the machine on which Meridio for Microsoft SharePoint is installed (see page 100). 2. Configure Kerberos security for Meridio for Microsoft SharePoint (see page 100). 3. Configure the machine which accesses Meridio for Microsoft SharePoint through Internet Explorer (see page 101). Configure delegation for the Meridio system (see page 101). Configuring Unified Login for Meridio Server The Meridio Server service is configured correctly for unified login as part of the installation process. Using the Administration client, add Meridio users to correspond to existing Windows users, either manually or by running an LDAP Directory Synchronisation task. Configuring Kerberos Security for Meridio Server Kerberos security must be configured on the Active Directory server for each Meridio Server which is not installed on the same machine as Meridio SOAP (as in Scenario 2). If the Windows user account running the Meridio services is a member of the Domain Admins group, Kerberos security for the Meridio Server is configured during installation. If the account is not a member of Domain Admins group, configure Kerberos security for the Windows user account with local administrator privileges. Use ADSI Edit to edit the properties for the user account to allow HTTP requests from the machine on which Meridio Server is installed, as follows: 1. In Microsoft Manager Console, load ADSI Edit. (See the Microsoft Manager Console help for details.) 2. In the tree view, expand the nodes to view the user. Right-click on the user account and select Properties from the shortcut menu to display the Properties dialog box. 3. If the account that Meridio services are running under is not a domain administrator, then the serviceprincipalname must be in the format: Meridio/MeridioServerName where MeridioServerName is the full network name of the server, e.g. mo.meridio.com 4. Click OK to apply the changes. Other Active Directory editing applications are available, but we strongly recommend the use of ADSI Edit, which can be installed from the Windows server installation disk. Configuring Unified Login for Meridio SOAP In Internet Information Services Manager, click Edit to edit authentication details for the MeridioSOAP virtual directory (on the Directory Security tab of the Properties dialog box). Select Integrated Windows authentication and clear Anonymous Access. Chapter 15 - Unified and Explicit Login 96

104 Configuring Kerberos Security for Meridio SOAP Kerberos security must be configured on the Active Directory server for a Windows user account with local administrator privileges. The user must be a member of the local IIS_WPG group. See Domain Users Configuration on page 20. Use ADSI Edit to edit the properties for the user account to allow HTTP requests from the machine on which Meridio SOAP is installed, as follows: 1. In Microsoft Manager Console, load ADSI Edit. (See the Microsoft Manager Console help for details.) 2. In the tree view, expand the nodes to view the user. Right-click on the user account and select Properties from the shortcut menu to display the Properties dialog box. 3. On the Attributes tab, select the serviceprincipalname property. Add the name of the machine on which Meridio SOAP is installed, as HTTP/machine.domain, e.g. HTTP/mo.meridio.com. 4. Click OK to apply the changes. Other Active Directory editing applications are available, but we strongly recommend the use of ADSI Edit, which can be installed from the Windows server installation disk. Configuring Unified Login for Meridio Web Services In Internet Information Services Manager, click Edit to edit authentication details for the following virtual directories (on the Directory Security tab of the Properties dialog box): DMWS DWWS Select Integrated Windows authentication and clear Anonymous Access. If clients older than Meridio 4.3 are used with the Meridio web services, Anonymous Access should also be cleared for the MeridioSearch virtual directory; this virtual directory is provided for backwards compatibility. For the RMWS virtual directory, select Anonymous Access and ensure that the account specified for anonymous access is a member of the local IIS_WPG group. Edit web.config for the DM Web Service, located in Install_Drive:\Root_Folder\Web Services\DMWS. In <system.web>, uncomment the lines for unified login: <identity impersonate= true /> Restart IIS. Configuring Kerberos Security for Meridio Web Services Kerberos security must be configured on the Active Directory server for a Windows user account with local administrator privileges. See Domain Users Configuration on page 20. Chapter 15 - Unified and Explicit Login 97

105 Use ADSI Edit to edit the properties for the user account to allow HTTP requests from the machine on which Meridio Web Services are installed, as follows: 1. In Microsoft Manager Console, load ADSI Edit. (See the Microsoft Manager Console help for details.) 2. In the tree view, expand the nodes to view the user. Right-click on the user account and select Properties from the shortcut menu to display the Properties dialog box. 3. On the Attributes tab, select the serviceprincipalname property. Add the name of the machine on which Meridio Web Services are installed, as HTTP/machine.domain, e.g. HTTP/mo.meridio.com. 4. Click OK to apply the changes. Other Active Directory editing applications are available, but we strongly recommend the use of ADSI Edit, which can be installed from the Windows server installation disk. To finish configuring Kerberos security, add the selected user account to the local iis_wpg group. In Internet Information Services Manager, specify the selected account for the application pool for the following virtual directories, on the Identity tab of the application pool s Properties dialog box: DMWS DWWS This account must not be set up as a Meridio user. See Domain Users Configuration on page 20. Configuring Unified Login for Meridio for Web Users To configure unified login for Meridio for Web Users, changes are necessary for any machines from which users will access Meridio for Web Users, as well as the machine on which Meridio for Web Users is installed. Configuring the Meridio for Web Users Machine In Internet Information Services Manager, click Edit to edit authentication details for the following virtual directories (on the Directory Security tab of the Properties dialog box): Meridio Search Select Integrated Windows authentication and clear Anonymous Access. Edit web.config for Meridio for Web Users, located in Install_Drive:\Root_Folder\WebServices\Meridio. Comment the lines for standard login: <authentication mode= Forms > <forms name= login path= / loginurl= login/loginform.aspx /> </authentication> <authorization> <deny users=? /> </authorization> Uncomment the lines for unified login: <authentication mode= Windows /> <identity impersonate= true /> Chapter 15 - Unified and Explicit Login 98

106 <authorization> <allow users= * /> <deny users=? /> </authorization> If you want to disable the use of standard login (in other words, to prevent users of Meridio for Web Users from logging in except with unified login), change the value of the following line from False to True: <add key= DisableStandardLogin value= false /> Restart IIS. Configuring Kerberos Security for the Meridio for Web Users Machine Kerberos security must be configured on the Active Directory server for a Windows user account with local administrator privileges. See Domain Users Configuration on page 20. Use ADSI Edit to edit the properties for the user account to allow HTTP requests from the machine on which Meridio for Web Users is installed, as follows: 1. In Microsoft Manager Console, load ADSI Edit. (See the Microsoft Manager Console help for details.) 2. In the tree view, expand the nodes to view the user. Right-click on the user account and select Properties from the shortcut menu to display the Properties dialog box. 3. On the Attributes tab, select the serviceprincipalname property. Add the name of the machine on which Meridio for Web Users is installed, as HTTP/machine.domain, e.g. HTTP/mo.meridio.com. 4. Click OK to apply the changes. Other Active Directory editing applications are available, but we strongly recommend the use of ADSI Edit, which can be installed from the Windows server installation disk. To finish configuring Kerberos security, add the selected user account to the local iis_wpg group. In Internet Information Services Manager, specify the selected account for the Meridio application pool, on the Identity tab of the Properties dialog box. This account must not be set up as a Meridio user. See Domain Users Configuration on page 20. Configuring Machines Accessing Meridio for Web Users In the web browser, select Enable Integrated Windows Authentication (on the Advanced tab of the Internet Options dialog box). On the Security tab of the Internet Options dialog box, add the name of the machine on which Meridio for Web Users is installed to the list of trusted sites. Edit the security level for trusted sites (click Custom Level) and select Automatic logon with current name and password. Restart Internet Explorer if required. Chapter 15 - Unified and Explicit Login 99

107 Configuring Meridio for Microsoft SharePoint To configure unified login for Meridio for Microsoft SharePoint, changes are necessary for any machines from which users will access Meridio for Microsoft SharePoint, as well as the machine on which Meridio for Microsoft SharePoint is installed. Configuring the Meridio for Microsoft SharePoint Machine Edit web.config for Microsoft SharePoint, located in the root folder for the web site, e.g. C:\inetpub\wwwroot. Locate the following line, and change value to True: <add key= Meridio.Web.Clients.SharePoint.UseUnifiedLogin value= False /> On the machine on which the Search Protocol Handler is installed, edit SPSMeridioInt.cfg, located in SharePoint_Installation\SearchProtocol. Comment the lines which begin: <Variable name= IndexUser <Variable name= IndexPassword Ensure that the account which runs the SharePointPS Search service (Microsoft SharePoint 2003) or Office SharePoint Server Search service (Microsoft SharePoint 2007) is a Meridio user. Restart the Search service. Configuring Kerberos Security for Meridio for Microsoft SharePoint Kerberos security must be configured as follows for an NT user account with local administrator privileges. This should not be the same account as the one used to run Meridio services or the SQL server. Use ADSI Edit to edit the properties for the user account to allow HTTP requests from the machine on which Meridio for SharePoint is installed, as follows: 1. In Microsoft Manager Console, load ADSI Edit. (See the Microsoft Manager Console help for details.) 2. In the tree view, expand the nodes to view the CN=Users node. Right-click on the user account and select Properties from the shortcut menu to display the Properties dialog box. 3. On the Attributes tab, select the serviceprincipalname property. Add the name of the machine on which Meridio for SharePoint is installed, as HTTP/machine.domain, e.g. HTTP/mo.meridio.com. 4. Click OK to apply the changes. Other Active Directory editing applications are available, but we strongly recommend the use of ADSI Edit, which can be installed from the Windows server installation disk. Add the selected user account to the local iis_wpg group. In Internet Information Services Manager, specify the selected account for the Meridio application pool, on the Identity tab of the Properties dialog box. This account must not be set up as a Meridio user. See Domain Users Configuration on page 20. Stop IIS. Configure Microsoft SharePoint to use Kerberos authentication by editing the file %systemroot%\system32\inetsrv\metabase.xml. In the <IISWebServer> section change: Chapter 15 - Unified and Explicit Login 100

108 NTAuthenticationProviders= NTLM to: NTAuthenticationProviders= Negotiate,NTLM There can be multiple NTAuthenticationProviders nodes, depending on the number of web sites on the server. Restart IIS. Configuring Machines Accessing Meridio for Microsoft SharePoint In the web browser (Internet Explorer 6 with Service Pack 1), select Enable Integrated Windows Authentication (on the Advanced tab of the Internet Options dialog box). On the Security tab of the Internet Options dialog box, add the name of the Microsoft SharePoint Portal Server on to the list of trusted sites. Edit the security level for trusted sites (click Custom Level) and select Automatic logon with current name and password. Restart Internet Explorer if required. Configuring Delegation Delegation requires a number of settings on the Domain Controller of the network for the recommended system architecture. It is not required if Meridio Server, Meridio Web Services and Meridio for Web Users are installed on the same machine. For the account under which the ASP.NET worker process runs (i.e. the Application Pool account see Domain Users Configuration on page 20): Trusted for delegation must be selected. Account is sensitive and cannot be delegated must be cleared. For the machines 1, 2 and 3 (as illustrated in the diagrams on page 1), i.e. the machines on which the Meridio server, Meridio SOAP, Meridio Web Services and Meridio for Web Users are installed: Trusted for delegation must be selected. Wait approximately 15 minutes before testing unified logon, to allow these settings to be propagated. Explicit Login Explicit Login is a method of gaining authenticated access to a Meridio system using Meridio login credentials. The user must enter their username and password when prompted to do so. To configure explicit login successfully, the steps in the following checklist must be completed: Configure the Meridio Server (see page 102). Configure Meridio SOAP (see page 102). Configure Meridio Web Services (see page 102). Chapter 15 - Unified and Explicit Login 101

109 Configure Meridio for Web Users: 1. Configure the machine on which Meridio for Web Users is installed (see page 103). 2. Configure the machine which accesses Meridio for Web Users through Internet Explorer (see page 103). If relevant, configure Single Sign-on for Meridio for Microsoft SharePoint. See SharePoint Single Sign-On Authentication on page 121 (in Chapter 18, Meridio for Microsoft SharePoint Configuration Settings ). Configuring Explicit Login for Meridio Server No changes are necessary for the Meridio Server service, since it is configured correctly for explicit login as part of the installation process. Configuring Explicit Login for Meridio SOAP In Internet Information Services Manager, click Edit to edit authentication details for the MeridioSOAP virtual directory (on the Directory Security tab of the Properties dialog box). Clear Integrated Windows authentication and select Anonymous Access. Set the user for Anonymous Access to a network user with appropriate permissions. Enter the user s password. Restart the Meridio Server and IIS services. Configuring Explicit Login for Meridio Web Services In Internet Information Services Manager, click Edit to edit authentication details for the following virtual directories (on the Directory Security tab of the Properties dialog box): DMWS DWWS Clear Integrated Windows authentication and select Anonymous Access. Set the user for Anonymous Access to a network user with appropriate permissions. If clients older than Meridio 4.3 are used with the Meridio web services, Anonymous Access should also be selected for the MeridioSearch virtual directory; this virtual directory is provided for backwards compatibility. Edit web.config for the DM web service, located in Install_Drive:\Root_Folder\Web Services\DMWS. In <appsettings>, comment the lines for unified login: <identity impersonate= true /> Restart IIS. Configuring Explicit Login for Meridio for Web Users To configure explicit login for Meridio for Web Users, changes are necessary for any machines from which users will access Meridio for Web Users, as well as the machine on which Meridio for Web Users is installed. Chapter 15 - Unified and Explicit Login 102

110 Configuring the Meridio for Web Users Machine In Internet Information Services Manager, click Edit to edit authentication details for the following virtual directories (on the Directory Security tab of the Properties dialog box): Meridio Search Clear Integrated Windows authentication and select Anonymous Access. Set the user for Anonymous Access to a network user with appropriate permissions. Edit web.config for the Meridio for Web Users, located in Install_Drive:\Root_Folder\WebServices\Meridio. Uncomment the lines for standard login: <authentication mode= Forms > <forms name= login path= / loginurl= login/loginform.aspx /> </authentication> <authorization> <deny users=? /> </authorization> Comment the lines for unified login: <authentication mode= Windows /> <identity impersonate= true /> <authorization> <allow users= * /> <deny users=? /> </authorization> If standard logins have been disabled (in other words, to prevent users of Meridio for Web Users from logging in except with unified login), change the value of the following line from True to False: <add key= DisableStandardLogin value= true /> Restart IIS. Configuring Machines Accessing Meridio for Web Users In the web browser, clear Enable Integrated Windows Authentication (on the Advanced tab of the Internet Options dialog box). Restart Internet Explorer if required. Chapter 15 - Unified and Explicit Login 103

111 CHAPTER 16 Meridio Web Services Configuration Settings This chapter describes the configuration settings for Meridio Web Services. See Chapter 17, Meridio for Web Users Configuration Settings, for configuration settings which apply to Meridio for Web Users. Regional Settings By default, Meridio Web Services is configured to display dates as English (United Kingdom), e.g. DDMMYYYY. The date format can be modified to any number of culture formats by editing the web.config file in the following folders (located by default in C:\Meridio\WebServices): DMWS RMWS SCWS Change the value of the following <appsetting> to the appropriate culture, e.g. en-us for United States: <add key= InstallationCulture value = en-gb /> See Chapter 17, Meridio for Web Users Configuration Settings, for information about changing the date format for Meridio for Web Users. File Transfer and Launching Files can be transferred using either DIME or UNC transfer methods. By default Meridio is configured to use Direct Internet Message Encapsulation (DIME) for uploads and downloads in Meridio for Web Users. DIME is a packaging mechanism that allows multiple records of arbitrarily formatted data to be streamed together. DIME provides a means of uploading and downloading files without the need to share folders. Meridio for Web Users can be configured to use UNC instead of DIME for uploads and downloads see File Transfer and Launching on page 110 in Chapter 17, Meridio for Web Users Configuration Settings. In general, if working with large documents (greater than 50MB) : UNC is faster than DIME. UNC uses less memory than DIME. UNC may reduce the need to make timeout configurations because it is quicker. After making any changes to the DIME or UNC configuration, you must restart IIS. Chapter 16 - Meridio Web Services Configuration Settings 104

112 DIME Configuration The following table describes the settings for DIME for the machine on which Meridio SOAP is installed. Restart IIS after making changes. Location of Setting drive:\soap_shared_folder Setting/Key DIME does not require the SOAP shared folder to be shared or permissions to be set so it is possible to unshare it however, there are security and functional implications. If you are using unified login then all Meridio end user accounts must have read/write access (specifically list folder/read data, read attributes, read extended attributes, create files/write data and read permissions) to the unshared SOAP folder. If you are using unified login then all Meridio end user accounts must have read/write access (specifically list folder/read data, read attributes, read extended attributes, create files/write data and read permissions) to the unshared SOAP folder. In addition, the account under which the DefaultAppPool Application Pool in IIS is configured must also have read/write access (specifically list folder/read data, read attributes, read extended attributes, create files/write data, read permissions) and delete permission to the unshared SOAP folder. This is to ensure files are deleted successfully during failed uploads. If you are not using unified login then the accounts under which the DMWS and MeridioSOAP virtual directories run must have read/write access (specifically list folder/read data, read attributes, read extended attributes, create files/write data and read permissions) to the unshared SOAP folder. In addition, the account under which the DefaultAppPool Application Pool in IIS is configured (default is preconfigured to Network Service) must have create files/write data and delete permissions to the unshared SOAP folder. WARNING: other functionality in Meridio uses the SOAP Share and requires full permissions for Everyone to be set, otherwise it will fail. We therefore recommend that you leave the SOAP folder shared with permissions set to allow everyone full control. Chapter 16 - Meridio Web Services Configuration Settings 105

113 Location of Setting HKEY_LOCAL_MACHINE\SOFTWARE \Meridio Ltd\MeridioSOAP Setting/Key DownloadFolderUNC set the value to the local path to the SOAP_shared_folder instead of the UNC path. UNC Configuration The following table describes the settings for UNC for the machine on which Meridio SOAP is installed. Restart IIS after making changes. Location of Setting drive:\soap_shared_folder HKEY_LOCAL_MACHINE\SOFTWARE \Meridio Ltd\MeridioSOAP Setting/Key Ensure the folder is shared with the permissions and security set to allow Full Control to Everyone. (The folder is shared by default.) DownloadFolderUNC set the value to the UNC path to the SOAP_shared_folder. Size Limit ASP.NET imposes a size limit on file uploads, which limits the size of files that may be uploaded. This is configurable by editing the following value in the DM Web Service web.config file (located in Install_Drive:\Root_Folder\Web Services\DMWS\): <httpruntime maxrequestlength= executiontimeout= 900 /> In this example, the size limit has been increased to 10MB. You also need to locate the following element and change its value (in kilobytes) as follows (in this case, to allow a 10MB file limit): <microsoft.web.services2> <messaging> <maxrequestlength>10240</maxrequestlength> </messaging> <diagnostics /> </microsoft.web.services2> In addition, IIS 6 on Windows Server 2003 imposes a limit on the amount of data that may be transferred in the body of an ASP request. The default value for this is 200 KB, which is insufficient for certain activities in Meridio Web Services, such as adding or launching a document that is larger than that size. If the limit is exceeded, IIS can return a 403 error response. You should change the default setting as follows: 1. Launch IIS Manager, right-click on the local computer, select Properties and select the Enable Direct Metabase Edit check box. 2. Using Notepad, open the file metabase.xml in %systemroot%\system32\inetsrv. 3. Find the entry AspMaxRequestEntityAllowed and change its value (in bytes) to a larger number, e.g (10 MB). Chapter 16 - Meridio Web Services Configuration Settings 106

114 4. A separate entry in metabase.xml limits the number of bytes that an ASP page can write to the response buffer before a flush occurs. This limit defaults to 4 MB and may impact large file downloads. To adjust it, find the variable named AspBufferingLimit and change its value (in bytes) to a larger number, e.g (10 MB). Timeouts Operations that may take a long time (for example, transferring a large file) may cause timeout exceptions to be reported from the DM Web Service. These errors may be avoided by increasing the values of a number of configuration settings. These changes include changes to the machine.config file, as well as registry changes that affect Meridio SOAP. These changes will not take effect until IIS is restarted. The following table describes the timeout settings for the machine on which Meridio SOAP and Meridio Web Services are installed. Application Location of Setting Setting/Key Default Recomme nded MeridioSOAP DMWS IIS Manager > MeridioSOAP Properties dialog box > Virtual Directory tab > click Configuration > Options tab HKEY_LOCAL_MACHINE \ SOFTWARE\Meridio Ltd\MeridioSOAP IIS Manager > DMWS Properties dialog box > Virtual Directory tab > click Configuration > Options tab ASP script timeout 90s 900s DefaultTemp FileLifetime 20s 900s ASP script timeout 90s 900s C:\Meridio\Webservices \DMWS\web.config <httpruntime> element executiontimeout attribute 90s 900s Not required if Meridio for Web Users uses Meridio web services in-process. <add key= sqlcommandtimeout value= 30 /> 30s 900s RMWS IIS Manager > RMWS Properties dialog box > Virtual Directory tab > click Configuration > Options tab ASP script timeout 90s 900s Chapter 16 - Meridio Web Services Configuration Settings 107

115 Application Location of Setting Setting/Key Default Recomme nded C:\Meridio\Webservices \RMWS\web.config <httpruntime> element executiontimeout attribute 90s 900s Not required if Meridio for Web Users uses Meridio web services in-process. <add key= sqlcommandtimeout value= 30 /> 30s 900s SCWS IIS Manager > SCWS Properties dialog box > Virtual Directory tab > click Configuration > Options tab ASP script timeout 90s 900s C:\Meridio\Webservices \SCWS\web.config <httpruntime> element executiontimeout attribute 90s 900s Not required if Meridio for Web Users uses Meridio web services in-process. <add key= sqlcommandtimeout value= 30 /> 30s 900s.NET framework \%systemroot%\ Microsoft.NET\ Framework\version\ Config\machine.config <processmodel> element responsedeadlockinterval attribute 00:03:00 (3 mins) 15 mins Ensure that this value is greater than the timeout values specified in the <httpruntime> executiontimeout One situation in which a timeout may easily occur is when retrieving HTML conversions of large PDF documents. Meridio SOAP s conversion of PDF to HTML is very slow, due to limitations in the third-party software used by Meridio SOAP to perform the conversion. The result is that PDF-to-HTML conversion requests typically time out under the default configuration. It is recommended that HTML conversion is avoided for large PDF documents. Chapter 16 - Meridio Web Services Configuration Settings 108

116 IIS Security Settings The default security settings of IIS 6 on Windows Server 2003 do not allow the Meridio Web Services to run. You must change the default settings as follows: In Internet Information Services (IIS) Manager, under Web Service Extensions, you must allow the following options: Active Server Pages ASP.NET v If unified login is not configured, in Internet Information Services (IIS) Manager, change the account used for anonymous access within Directory Security properties from the default IUSR_computername account to a domain account, for the following virtual directories: DMWS DWWS RMWS MeridioSOAP SCWS If unified login is configured, setting anonymous access on the virtual directories, except for RMWS and SCWS, will cause it to stop working. If clients older than Meridio 4.3 are used with the Meridio web services, the account for anonymous access should also be changed for the MeridioSearch virtual directory; this virtual directory is provided for backwards compatibility. The EncryptAuthToken key in the MeridioSearch web.config file must also have the same value as the EncryptAuthToken key in the Meridio for Web Users web.config file (see Meridio for Web Users Security Settings on page 113). Client Access to Meridio Web Services In order for Meridio client applications to access the Meridio Web Services, the name of the Web Services machine (or web server farm) must be set in the system properties this is done in Meridio Administration, on the Servers tab of the System Properties dialog box. See Chapter 3 of Meridio for System Administrators for more information. Installing the Meridio Records Management Database Upgrade automatically sets the name of the Web Services machine. Chapter 16 - Meridio Web Services Configuration Settings 109

117 CHAPTER 17 Meridio for Web Users Configuration Settings This chapter describes the various configuration settings for Meridio for Web Users. Some settings are configured in Meridio for Web Users web.config; this is located by default in: C:\Meridio\WebServices\Meridio, if installed with Meridio Web Services C:\Meridio\WebClient\Meridio, if installed separately Regional Settings By default, Meridio for Web Users is configured to display dates as English (United Kingdom), e.g. DDMMYYYY. The date format can be modified to any number of culture formats by editing the web.config file in the Meridio and Search folders (located by default in C:\Meridio\WebServices or C:\Meridio\WebClient). Change the value of the following <appsetting> to the appropriate culture, e.g. en-us for United States: <add key= InstallationCulture value = en-gb /> File Transfer and Launching Files can be transferred using either DIME or UNC transfer methods. By default Meridio is configured to use Direct Internet Message Encapsulation (DIME) for uploads and downloads in Meridio for Web Users. DIME is a packaging mechanism that allows multiple records of arbitrarily formatted data to be streamed together. DIME provides a means of uploading and downloading files without the need to share folders. Meridio for Web Users can be configured to use UNC instead of DIME for uploads and downloads. Changes are also made for Meridio SOAP and Meridio Web Services. See File Transfer and Launching on page 104 in Chapter 16, Meridio Web Services Configuration Settings. In general, if working with large documents (greater than 50MB): UNC is faster than DIME. UNC uses less memory than DIME. UNC may reduce the need to make timeout configurations because it is quicker. After making any changes to the DIME or UNC configuration, you must restart IIS. Chapter 17 - Meridio for Web Users Configuration Settings 110

118 DIME Configuration The following table describes the settings for DIME for the machine on which Meridio for Web Users is installed. Location of Setting C:\Meridio\Webservices\Meridio\ web.config or C:\Meridio\Webclient\ Meridio\web.config (if Meridio for Web Users is installed separately to Meridio Web Services) C:\Meridio\Webservices\Meridio\ Upload\ or C:\Meridio\Webclient\ Meridio\Upload (if Meridio for Web Users is installed separately to Meridio Web Services) Setting/Key In the ConnectionString key, set UNCContentTransfer=false. (The default value is false.) DIME does not require the upload folder to be shared or permissions to be set so it is possible to unshare it however, there are security and functional implications. If you are using unified login, all Meridio end user accounts must have read/write access (specifically list folder/read data, read attributes, read extended attributes, create files/write data, read permissions) and delete permissions. If you are not using unified login, then the account under which the DefaultAppPool Application Pool in IIS is configured (by default, Network Service) must have read/write access (specifically list folder/read data, read attributes, read extended attributes, create files/write data and read permissions) and create files/write data and delete permissions. UNC Configuration The following table describes the settings for UNC for the machine on which Meridio for Web Users is installed. Location of Setting C:\Meridio\Webservices\Meridio\ web.config or C:\Meridio\Webclient\ Meridio\web.config (if Meridio for Web Users is installed separately to Meridio Web Services) Setting/Key In the ConnectionString key: Set UNCContentTransfer=true. (The default value is false.) Set UNCUploadPath to the UNC path of the SOAP shared folder. Set UNCTempUploadPath to the UNC path of the SOAP shared folder. Chapter 17 - Meridio for Web Users Configuration Settings 111

119 Size Limit ASP.NET imposes a size limit on file uploads, which limits the size of files that may be uploaded. This is configurable by editing the following value in the Meridio for Web Users web.config file: <httpruntime maxrequestlength= executiontimeout= 900 /> In this example, the size limit has been increased to 10MB. You also need to locate the following element and change its value (in kilobytes) as follows (in this case, to allow a 10MB file limit): <microsoft.web.services2> <messaging> <maxrequestlength>10240</maxrequestlength> </messaging> <diagnostics /> </microsoft.web.services2> In addition, IIS 6 on Windows Server 2003 imposes a limit on the amount of data that may be transferred in the body of an ASP request. The default value for this is 200 KB, which is insufficient for certain activities in Meridio for Web Users, such as adding or launching a document that is larger than that size. If the limit is exceeded, IIS can return a 403 error response or Meridio for Web Users can return an error message such as 0, This is an unexpected token. The expected token is EndElement. Line 1, position 323. You should change the default setting as follows: 1. Launch IIS Manager, right-click on the local computer, select Properties and select the Enable Direct Metabase Edit check box. 2. Using Notepad, open the file metabase.xml in %systemroot%\system32\inetsrv. 3. Find the entry AspMaxRequestEntityAllowed and change its value (in bytes) to a larger number, e.g (10 MB). 4. A separate entry in metabase.xml limits the number of bytes that an ASP page can write to the response buffer before a flush occurs. This limit defaults to 4 MB and may impact large file downloads. To adjust it, find the variable named AspBufferingLimit and change its value (in bytes) to a larger number, e.g (10 MB). Timeouts Operations that may take a long time (for example, transferring a large file) may cause timeout exceptions to be reported from Meridio for Web Users. These errors may be avoided by increasing the values of a number of configuration settings. The following table describes the timeout settings for the machine on which Meridio for Web Users is installed. Application Location of Setting Setting/Key Default Recommended Meridio for Web Users IIS Manager > Meridio Properties dialog box > Virtual Directory tab > click Configuration > Options tab ASP script timeout 90s 900s Chapter 17 - Meridio for Web Users Configuration Settings 112

120 Application Location of Setting Setting/Key Default Recommended C:\Meridio\Webservices \Meridio\web.config or C:\Meridio\Webclient\ Meridio\web.config (if Meridio for Web Users is installed separately to Meridio Web Services) If Meridio for Web Users is configured to use Web Services in-process, add the following <appsetting> copied from web.config for DMWS: Meridio.Web.Services.DM. SOAPTimeout ms (100s) ms (900s) <httpruntime> element executiontimeout attribute 90s 900s <add key= ConnectionString value= timeout:100000; ms (100s) ms (900s) <add key= sqlcommandtimeout value= 30 /> 30s 900s.NET framework \%systemroot%\ Microsoft.NET\ Framework\version\ Config\machine.config <processmodel> element responsedeadlockinterval attribute 00:03:00 (3 mins) 15 mins Ensure that this value is greater than the timeout values specified in the <httpruntime> executiontimeout One situation in which a timeout may easily occur is when retrieving HTML conversions of large PDF documents. Meridio SOAP s conversion of PDF to HTML is very slow, due to limitations in the third-party software used by Meridio SOAP to perform the conversion. The result is that PDF-to-HTML conversion requests typically time out under the default configuration. It is recommended that HTML conversion is avoided for large PDF documents. Security Settings Security settings for Meridio for Web Users are changed in the relevant web.config file and in IIS Manager. Meridio for Web Users Security Settings The Meridio for Web Users web.config file includes the following appsetting: <add key= Meridio.Web.Clients.EDRM.EncryptAuthToken value= true /> which causes each authorisation token passed to the Meridio Server to be encrypted. The encryption is unique for each user as it is based on their IP address. This setting is enabled by default, but can be disabled (the value set to false ) if the system performance is degraded, e.g. in a system with a very large number of users. Chapter 17 - Meridio for Web Users Configuration Settings 113

121 The EncryptAuthToken key must have the same value in the Search web.config file (located by default in C:\Meridio\WebServices\Search) as the EncryptAuthToken key in the Meridio for Web Users web.config file. On the machine on which Meridio Web Services are installed, write access must be set on the temporary files directory (normally C:\Windows\Temp) for the Everyone or the Domain Users group. This is necessary for browsers on other machines to access Meridio for Web Users. IIS Security Settings The default security settings of IIS 6 on Windows Server 2003 do not allow Meridio for Web Users to run. You must change the default settings as follows: In Internet Information Services (IIS) Manager, under Web Service Extensions, you must allow the following options: Active Server Pages ASP.NET v If unified login is not configured, in Internet Information Services (IIS) Manager, change the account used for anonymous access within Directory Security properties from the default IUSR_computername account to a domain account, for the following virtual directories: Meridio Search Restricting File Types To reduce the risk of users opening documents that are infected with viruses, an entry can be added to web.config to limit the types of files that can be opened with Meridio for Web Users. In the web.config file for Meridio for Web Users, add the appropriate entries below the entry which starts: <!-- List the file extensions that cannot be launched directly from within Meridio. Instead, files of these types will be converted to HTML where possible and displayed inline. This config setting is useful for preventing users from uploading virus infected.exe files for other user to launch by mistake. Each file extension value is separated by a comma and must include the prefix. The format for this setting is:- <add key= MeridioRestrictedFileExtensions value=.xxx,.xxx ></add> --> For example, to restrict files of the type.jpg and.png, add an entry of: <add key= MeridioRestrictedFileExtensions value=.jpg,.png ></add> Chapter 17 - Meridio for Web Users Configuration Settings 114

122 Miscellaneous Meridio for Web Users Settings The following settings are configured in Meridio for Web Users web.config. Meridio for Web Users View State Settings A web.config entry exists to allow the view state of Meridio for Web Users to be saved to the server in a state database. If using SQL Server for the database, the database can be created by running a SQL script InstallSqlStat.sql, supplied with the.net framework in SQL Query Analyzer. The database created is ASPState. In the Meridio for Web Users web.config file, edit the following entry: <!-- Enable/Disable Server Side View State --> <add key= ServerSideViewState value= false /> and set the value to true. You can also configure the number of view states that should be saved per session (the default is 20): <add key= NumServerSideViewStatePages value= 20 /> and whether the viewstates should be compressed (the default is false): <add key= CompressViewState value= false /> Configuring the Timeout for Temporary Files When a document is added to Meridio using Meridio for Web Users, it is deleted from the temporary files directory after a specified amount of time (the default is five minutes). If longer than this time elapses between selecting the document and submitting it to Meridio (by saving or declaring as a record), errors can occur. In the Meridio for Web Users web.config file, edit the following entry: <!-- The time span for the Temporary File CleanUp task to delete the file. If no value is provided the task will be defaulted for 5 minutes.--> <!-- The value should be in minutes --> <add key= CleanUpTaskTimeSpan value= 5 /> and set the value to the number of minutes after which temporary files should be deleted. Configuring Meridio for Web Users to Accept < and > Characters When trying to update the To, From, CC and BCC properties on a document in the Mail Message category, a problem occurs because ASP will not allow text areas to be submitted with < or > characters in the text. To resolve this problem, you must disable request validation for Merido for Web Users. Edit web.config for Meridio for Web Users, and set the validaterequest attribute of the <PAGES /> section to false: <configuration> <system.web> <pages validaterequest= false /> </system.web> </configuration> If this is done, then Meridio for Web Users is open to script injection attacks, because the text from fields sent back to the server is not all HTML-encoded. Chapter 17 - Meridio for Web Users Configuration Settings 115

123 Changing the Number of Users/Groups Displayed You can change the number of users or groups displayed in the search results when, for example, adding access control entries. Edit web.config for Meridio for Web Users, and change the value of the following entry to the maximum number of users/groups that you want displayed: MaxNumUserOrGroup= 100 The default value is 100; this is also used if the value set is invalid. Configuring Federated Search The Search web application can be configured so that users can search multiple Meridio systems using Meridio for Web Users and Meridio for Microsoft Outlook. Unified login must be configured for users to access the Meridio systems. The EncryptAuthToken key must have the same value in the Search web.config file (located by default in C:\Meridio\WebServices\Search) as the EncryptAuthToken key in the Meridio for Web Users web.config file see Meridio for Web Users Security Settings on page 113. To configure federated search: 1. For each Meridio system, edit web.config for the Search web application, located by default in C:\Meridio\Webservices\Search. 2. Under <configuration>, add the following: <federationconfiguration> </federationconfiguration> 3. Add the following under <federationconfiguration> for the system you are connecting from (System A). The first <systemroute> must define the system itself; subsequent <systemroute> sections define the systems it will search, e.g. (System B). <system> <systemname>meridio System A</systemName> <!--The name of the Meridio system --> <location>some Town</location> <!--Some location information.--> <comment>head Office, Human Resources</comment> <!--A comment to help users understand what the system is used for.--> <contactname>mr. Smith</contactName> <!--A contact name should a problem arise.--> <contact address>contact address@test.com</contact address> <!--An address for the contact person.--> <systemroutes> <!--The SystemRoutes collection is used to determine the best web services to use when connecting the system defined above from another system.--> <systemroute> <sourcesystemname>meridio System A</sourceSystemName> <!-- The name of the system the user will log onto to search the Meridio system (System A).--> <connectionstring>timeout=100000;dmwsuri= /meridiodmws.asmx;rmwsuri= x;ruwsuri= rvices=false</connectionstring> <!--The location of the web services for System A.--> <connectionspeed>excellent</connectionspeed> Chapter 17 - Meridio for Web Users Configuration Settings 116

124 <!-- A user defined value to describe the connection quality between the machine defined in sourcesystemname and systemname. Values can be Excellent, VeryGood, Good, Average, BelowAverage and Poor--> <add key= TargetedWebClientMachineName >WebClientMachineforA</add> <!-- The location of the Meridio Web for Users installation for System A.--> <add key= WebClientVirtualDirectory >Meridio</add> <!-- The virtual directory of the Meridio for Web Users installation for System A - by default, Meridio.--> </systemroute> <systemroute> <sourcesystemname>meridio System B</sourceSystemName> <!-- The name of the second system being searched (System B).--> <connectionstring>timeout=100000;dmwsuri= /meridiodmws.asmx;rmwsuri= x;ruwsuri= rvices=false</connectionstring> <!-- The location of the Meridio Web Services for System A.--> <connectionspeed>excellent</connectionspeed> <!-- A user defined value to describe the connection quality between the machine defined in sourcesystemname and systemname. Values can be Excellent, VeryGood, Good, Average, BelowAverage and Poor--> <add key= TargetedWebClientMachineName >WebClientMachineforA</add> <!-- The location of the Meridio Web for Users installation for System A.--> <add key= WebClientVirtualDirectory >Meridio</add> <!-- The virtual directory of the Meridio for Web Users installation for System A - by default, Meridio.--> </systemroute> </systemroutes> </system> 4. For each system that you want to connect to (e.g. System B), add the following. The first <systemroute> must define the system from which you are searching (System A); the second <systemroute> must define the system itself (System B). Subsequent <systemroute> sections can be added. <system> <systemname>meridio System B</systemName> <!--The name of the Meridio system --> <location>some Town</location> <!--Some location information.--> <comment>head Office, Human Resources</comment> <!--A comment to help users understand what the system is used for.--> <contactname>mr. Smith</contactName> <!--A contact name should a problem arise.--> <contact address>contact address@test.com</contact address> <!--An address for the contact person.--> <systemroutes> <!--The SystemRoutes collection is used to determine the best web services to use when connecting the system defined above from another system.--> <systemroute> <sourcesystemname>meridio System A</sourceSystemName> <!-- The name of the system the user will log onto to search the Meridio system (System A).--> <connectionstring>timeout=100000;dmwsuri= /meridiodmws.asmx;rmwsuri= x;ruwsuri= rvices=false</connectionstring> <!--The location of the Meridio Web Services for System B.--> <connectionspeed>excellent</connectionspeed> <!-- A user defined value to describe the connection quality between the machine defined in sourcesystemname and systemname. Values can be Excellent, VeryGood, Good, Average, BelowAverage and Poor--> <add key= TargetedWebClientMachineName >WebClientMachineforB</add> <!-- The location of the Meridio Web for Users installation for System B.--> <add key= WebClientVirtualDirectory >Meridio</add> <!-- The virtual directory of the Meridio for Web Users installation for System B - by default, Meridio.--> </systemroute> <systemroute> <sourcesystemname>meridio System B</sourceSystemName> <!-- The name of the second system being searched (System B).--> <connectionstring>timeout=100000;dmwsuri= Chapter 17 - Meridio for Web Users Configuration Settings 117

125 /meridiodmws.asmx;rmwsuri= x;ruwsuri= rvices=false</connectionstring> <!--The location of the Meridio Web Services for System B.--> <connectionspeed>excellent</connectionspeed> <!-- A user defined value to describe the connection quality between the machine defined in sourcesystemname and systemname. Values can be Excellent, VeryGood, Good, Average, BelowAverage and Poor--> <add key= TargetedWebClientMachineName >WebClientMachineforB</add> <!-- The location of the Meridio Web for Users installation for System B.--> <add key= WebClientVirtualDirectory >Meridio</add> <!-- The virtual directory of the Meridio for Web Users installation for System B - by default, Meridio.--> </systemroute> </systemroutes> </system> Running Meridio Web Services as a Remote Web Service For systems where the Meridio for Web Users client connects to a remote installation of Meridio Web Services, requests from the Meridio for Web Users client to the web services server are queued on the client machine if there are more than two requests. This is because the default setting for the maximum number of HTTP connections is two. To resolve this problem, edit machine.config on the Meridio for Web Users machine, located in the %installroot%\config directory, for example: C:\WINNT\Microsoft.NET\Framework\v \Config. N is the number of processors in the Meridio for Web Users machine. In the <connectionmanagement> section, set maxconnection= 12 x N e.g. maxconnection= 24 for a machine with two processors. In the <processmodel> section, set MaxIOThreads= 100 x N MaxWorkerThreads= 100 x N MinFreeThreads= 88 x N MinLocalRequestFreeThreads= 88 x N e.g. MaxIOThreads= 200 for a machine with two processors. Modifying Icons for Meridio for Web Users Document and record icons in Meridio for Web Users are composed of an icon to indicate the file type (e.g. Word document) and overlays which indicate the Meridio status (e.g. whether the file is a document or record, or whether the document is locked for editing). The icons which indicate file type can be replaced with custom icons, such as those installed with Microsoft SharePoint. If using icons other than those supplied by Meridio, you must have the necessary licence agreements in place. Chapter 17 - Meridio for Web Users Configuration Settings 118

126 Copy the icons you want to use into the following folders for the Meridio for Web Users installation (given for a default installation): C:\Meridio\Webservices\Meridio\Images\FileTypes (for general use in Meridio for Web Users) C:\Meridio\Webservices\Search\Images\FileTypes (for use in the Search pages in Meridio for Web Users) If Meridio for Web Users and Meridio Web Services are installed on separate machines, the location of the Meridio and Search folders is, by default, C:\Meridio\WebClient. The filename of the icon must be icextension.gif or icextension.png where EXTENSION is the file extension. For example, icdoc.png is the name of the installed icon file for a.doc file. If both GIF and PNG files exist for a file extension, the GIF is used. If the file extension is blank or there is no corresponding icon file, icgen.png is used. Chapter 17 - Meridio for Web Users Configuration Settings 119

127 CHAPTER 18 Meridio for Microsoft SharePoint Configuration Settings This chapter describes configuration settings for Meridio for Microsoft SharePoint 2003 and Meridio for Microsoft SharePoint Unless otherwise indicated, each setting described in this chapter applies to both versions of Meridio for Microsoft SharePoint. Meridio for Microsoft SharePoint 2007 Configuration For Meridio for SharePoint 2007, Meridio site features and the Meridio Storage Policy are activated by default. Meridio Site Features When Meridio features are activated at web application level (see Activating Meridio Web Application Features on page 85), they are automatically activated for any existing SharePoint web sites. The Meridio site features can be deactivated or activated if necessary for each site, from the Site Settings > Site Features page: Meridio Fileplan enables users to browse the Fileplan. Meridio Library Integration integrates Meridio with existing document libraries, for example, to enable users to save documents from document libraries to Meridio, create smart shortcuts to Meridio documents. The Meridio Fileplan feature must be activated to use this feature. Meridio Library Integration Refresh integrates Meridio with document libraries that are added subsequent to Meridio Library Integration being activated. This feature always appears inactive. If it is not activated, new document libraries do not have Meridio functionality. Meridio My Workspace enables users to browse their My Workspace. The Meridio Fileplan feature must be activated to use this feature. For a new document library, Meridio integration can be activated by selecting Activate Meridio Integration from the Settings menu. Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 120

128 Meridio Storage Policy If you wish to use MOSS policies when saving SharePoint documents to Meridio (see Meridio for System Administrators for more information), the Meridio Storage Policy must be activated. This takes places when the Meridio solution is deployed for a web application the Meridio Storage Policy feature is automatically activated at farm level (in other words, for all web applications). The Meridio Storage Policy can be deactivated if necessary, as follows: 1. On the Operations page, click Manage farm features. 2. On the Farm Features page, deactivate Meridio Storage Policy. SharePoint Single Sign-On Authentication Before users can access the Meridio document store, SharePoint single sign-on must be configured if unified login is not used; this allows account credentials to be stored and mapped. Refer to the SharePoint Portal Server Administration Guide. Once single sign-on is configured and running, you must create an enterprise application definition. Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 121

129 Single sign-on can only be configured on a system running Microsoft SharePoint Portal Server; it cannot be used on a system running Windows SharePoint Services. To specify the settings for single sign-on: 1. In SharePoint Portal Server Central Administration, in the Component Configuration section, click Manage settings for single sign-on. 2. On the Manage Settings for Single Sign-On screen, in the Enterprise Application Definition Settings section, click on Manage settings for enterprise application definitions. 3. On the Manage Enterprise Application Definitions screen, click the New Item toolbar button. 4. On the Create Enterprise Application Definition dialog box, do the following: i. In the Application and Contact Information section, enter Meridio into both Display and Application fields. An address must also be supplied that users can contact about the application. ii. In the Account type section, select Individual. iii. In the Logon Account Information section, enter Username in the Field 1 field and Password in the Field 2 field. For Field2, select Yes to hide the password typed by the user. 5. Click OK to create the new definition. Selecting Meridio Properties to Display on the Search Screen You can add, for example, Meridio Document Title to the list of properties that can be individually searched against; in other words, which appear in the drop-down list of searchable properties on the Search screen. In Microsoft SharePoint 2007, this is done from the Crawled Properties page in SharePoint Central Administration. For Microsoft SharePoint 2003, complete the following procedure. To add properties on the Manage Properties from Crawled Documents page in Microsoft SharePoint 2003: 1. From the portal root, click Site Settings. 2. In the Search Settings and Indexed Content section, navigate to Manage Properties from Crawled Documents. 3. Expand the urn:schemas.microsoft.com:htmlinfo:metainfo node in the tree. 4. The list of available properties should be shown below. The Meridio ones are all prefixed with Meridio. 5. To add a property to the search page, click on it, and select the Include this property in Advanced Search options check box. This automatically selects Include this property in the content index and Allow property to be displayed. 6. It is recommended that you perform a full index once new properties have been added. This is done from the Configure Search and Indexing dialog box, accessed by clicking Configure search and indexing on the Site Settings page. Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 122

130 If the additional properties are not immediately displayed, you must restart IIS to force it to recognise the changes. Web Configuration Settings The following changes are made in the web.config file, located in the root folder for the web site, e.g. C:\inetpub\wwwroot. File Upload Paths The web.config file includes the following appsettings: <add key= Meridio.Web.Clients.SharePoint.UploadPath value= C:\Meridio\SharePoint\Upload /> <add key= Meridio.Web.Clients.SharePoint.UNCTempUploadPath value= /> <add key= Meridio.Web.Clients.SharePoint.TempFileCleanUpInterval value= 5 /> The value of uploadpath specifies the folder in which files uploaded from end-users browsers are held temporarily. This key must have a value. The value of UNCTempUploadPath specifies the folder in which files uploaded using UNC are held temporarily. The value of TempFileCleanUpInterval specifies how often, in hours, the contents of the upload folders are deleted. Meridio Security Settings The web.config file includes the following appsetting: <add key= Meridio.Web.Clients.SharePoint.EncryptAuthToken value= true /> which causes each authorisation token passed to the Meridio Server to be encrypted. The encryption is unique for each user as it is based on their IP address. This setting is enabled by default, but can be disabled (the value set to false ) if the system performance is degraded, e.g. in a system with a very large number of users. Modifying the Number of Users/Groups Displayed in a Search You can change the number of users or groups displayed in the search results when, for example, adding access control entries. Edit web.config, and change the value of the following entry to the maximum number of users/groups that you want displayed: MaxNoUserOrGroup= 100 The default value is 100; this is also used if the value set is invalid. Integrating with Existing Document Libraries To integrate Meridio for Microsoft SharePoint with document libraries that existed before it was installed, the following key exists in the web.config file with a value of True: Meridio.Web.Clients.SharePoint.RunDocLibModifier If no document libraries existed before Meridio for Microsoft SharePoint was installed, it is recommended that the value is changed to False. Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 123

131 Configuring Smart Shortcuts for Documents Saved to Meridio You can set the type of smart shortcut created in a document library by changing the value of the following key in the web.config file: <add key= Meridio.Web.Clients.SharePoint.SmartShortcutFormat value= Typed /> Possible values are: Typed the smart shortcut retains the format of the original document, e.g. Microsoft Word HTML the smart shortcut is displayed as a HTML version of the original document By default, when a document in a document library is saved or declared as a record to Meridio, no reference to it remains in the document library. To create a smart shortcut in the document library for documents saved or declared to Meridio, change the value of the following key in the web.config file to False: Meridio.Web.Clients.Sharepoint.DeleteListItemOnSavingToFileplan Configuring the Meridio Document Properties You can configure Meridio so that when declaring a document from a SharePoint document library, Meridio auto-captures the value of the Meridio Title property from either the Title property or the Name property of the SharePoint document. This depends on the following key in the web.config file: <app key= Meridio.Web.Clients.SharePoint.CaptureNameForTitleProperty value= False /> If the value of this key is True, the Name property is auto-captured. If the value of this key is False, the Title property is auto-captured. You can also configure the property from which the Meridio Document Date is captured. Set the value of the following key to the name of the property: <app key= Meridio.Web.Clients.SharePoint.FileDateCreatedPropertyName value= propertyname /> Valid properties are: Date Created (default) Date Last Saved Displaying External Links Meridio for Microsoft SharePoint can be configured to displays links to external systems, such as other Meridio systems, on the All Items page. Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 124

132 Edit web.config and add a new section <Meridio.Web.Clients.SharePoint.ExternalLinks title= External Links showonallpages= true > as shown in the following example: <Meridio.Web.Clients.SharePoint.ExternalLinks title= External Links showonallpages= true > <group title= Shared Records in: > <link title= London url= tooltip= Meridio Records on London /> <link title= New York url= tooltip= Meridio Records on New York /> <link title= Tokyo url= tooltip= Meridio Records on Tokyo /> </group> <group title= Other Portals: > <link title= Los Angeles url= tooltip= SharePoint Portal for Los Angeles /> <link title= Mumbai url= tooltip= SharePoint Portal for Mumbai /> </group> </Meridio.Web.Clients.SharePoint.ExternalLinks> Configuring Context Menus By default, the option to display SharePoint version history for a document in a document library is disabled on the document context menu. To enable this option, change the value of the following key in the web.config file from False to True: Meridio.Web.Clients.SharePoint.ShowShortcutVersionHistoryContextMenu The following key in the web.config file is used to determine the options displayed on the document context menu: Meridio.Web.Clients.SharePoint.CheckoutContextMenuConfiguration Change the value as appropriate: options enables the Check Out command, which displays the check-out page on which the user can select to either check-out locally or check-out for collaboration (the default value) localcheckout enables the Local Check Out command, which checks the document out locally collaborate enables the Collaborate command, which checks the document out for collaboration Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 125

133 Using SharePoint Document Version Information in Meridio A Meridio custom property can be configured to contain the version information of a SharePoint document that has been saved or declared to the Meridio fileplan. To configure the Meridio custom property: 1. Edit the <appsettings> section of web.config (located in the root folder for the web site, e.g. C:\inetpub\wwwroot) by changing the value of the following to Summary: <add key= Meridio.Web.Clients.SharePoint.VersionHistoryImportAction value= None /> Note the value of the following, which can be changed if desired: <add key= Meridio.Web.Clients.SharePoint.VersionHistorySummaryPropertyName value= WSS Version History Summary /> The Meridio custom property which will contain the SharePoint document version information must be given this name. 2. In Meridio Administration, create a new document custom property with the name above, e.g. WSS Version History Summary. The custom property must be of type Long Text, and read-only. 3. Restart IIS for the changes to take effect. Now when a user saves or declares a SharePoint document to the Meridio fileplan, its document version information specifically the version number, author, date and comment will be copied to the custom property as a single string. Viewing SharePoint Document Versions in Meridio There is an option in the <appsettings> section of the web.config file which determines how many document versions are displayed in the Meridio Fileplan after declaring SharePoint documents to the Meridio Fileplan: <add key= Meridio.Web.Clients.SharePoint.DeleteAllPreviousVersionsOnSavingToFileplan value= True /> If value= True, the record version history will show only one Meridio version whether the original SharePoint document had one or more document versions. If value= False : if the original SharePoint document had only one version, the record version history displays one SharePoint version and one Meridio version if the original SharePoint document had multiple versions, the record version history displays all SharePoint versions and one Meridio version If the key does not exist or value=, the record version history is displayed as if value= False. Disabling the Protective Markings Warning for Collaboration When a document with protective markings is copied to a document library or checked out for collaboration, a warning message is displayed. This message can be disabled by changing the following key in the web.config file: Meridio.Web.Clients.SharePoint.ProtectiveMarkingDisplay The possible values are: 0 no warning displayed Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 126

134 1 simple warning displayed 2 full warning displayed Publishing Exceptions to the Event Log Exceptions, such as login exceptions, can be published to the event log by enabling the Meridio for SharePoint Exception Publisher, provided that users have the correct privileges to write to the event log. To enable the Meridio for SharePoint Exception Publisher, update web.config (located in the root folder for the web site, e.g. C:\inetpub\wwwroot) as follows: <configuration>... <exceptionmanagement mode= on > <publisher mode= on assembly= Meridio.Web.Clients.SharePoint,Version= ,Culture=neutral,Publ ickeytoken=dfbc b2f3 type= Meridio.Web.Clients.SharePoint.ExceptionPublisher exclude= System.Threading.ThreadAbortException /> </exceptionmanagement> </configuration> Alternatively it is possible to use a standard or custom publisher to write exception details to locations other than the event log. See the following article for more details: Configuring Meridio for Microsoft SharePoint for a WSS Installation For Meridio for Microsoft SharePoint to work correctly with a Windows SharePoint Services (WSS) installation on a system which also has SharePoint Portal Server (2003) or MOSS (2007), the following key must be added to the web.config file under <appsettings>: <add key= Meridio.Web.Clients.SharePoint.ForceWSSMode value= true /> Configuring Access to Multiple Systems Meridio system administrators can configure access to other Meridio systems. There are two ways in which other systems can be accessed via Meridio for Microsoft SharePoint: as links to individual classes on remote systems through the Meridio fileplan (federated fileplans) see Appendix C of Meridio for System Administrators as links to the entire Meridio system through the left-hand navigation bar (described here) Configuring Links to Other Systems If users have an account that enables them to log in on the remote system either via single sign-on (Microsoft SharePoint Portal Server only) or unified login, they can navigate to the remote system and work in it in the same way as the local system. To connect to multiple systems, Meridio for Microsoft SharePoint must be configured to contact the Meridio web services out-of-process (via HTTP). Edit web.config and set inprocesswebservices to False in the following key: <add key= Meridio.Web.Clients.SharePoint.ConnectionString /> Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 127

135 To enable access to other Meridio systems: 1. Edit the web.config file (located in the root folder for the web site, e.g. C:\inetpub\wwwroot). 2. Under <configsections>, add the following key: <section name= federationconfiguration type= Meridio.Clients.Libraries.Federation.FederationConfigurationSectionHan dler,meridio.clients.libraries.federation,version= ,culture=neutral,pu blickeytoken=dfbc b2f3 /> where Version is the version number for the Meridio for Microsoft SharePoint installation: for Meridio 5.0 SR-1 for Microsoft SharePoint for Meridio 5.0 SR-1 for Microsoft SharePoint Under <configuration>, add the following: <federationconfiguration> </federationconfiguration> 4. Add the following under <federationconfiguration> for the system you are connecting from, on which Meridio for Microsoft SharePoint is installed (System A). The first <systemroute> must define the system itself; subsequent <systemroute> sections define the systems it will connect to, e.g. (System B). <system> <systemname>meridio System A</systemName> <!--The name of the Meridio system --> <location>some Town</location> <!--Some location information.--> <comment>head Office, Human Resources</comment> <!--A comment to help users understand what the system is used for.--> <contactname>mr. Smith</contactName> <!--A contact name should a problem arise.--> <contact address>contact address@test.com</contact address> <!--An address for the contact person.--> <systemroutes> <!--The SystemRoutes collection is used to determine the best web services to use when connecting the system defined above from another system.--> <systemroute> <sourcesystemname>meridio System A</sourceSystemName> <!-- The name of the system on which Meridio for Microsoft SharePoint is installed (System A).--> <connectionstring>timeout=100000;dmwsuri= meridiodmws.asmx;rmwsuri= ;RUWSURI= vices=false</connectionstring> <!--The location of the web services for System A.--> <connectionspeed>excellent</connectionspeed> <!-- A user defined value to describe the connection quality between the machine defined in sourcesystemname and systemname. Values can be Excellent, VeryGood, Good, Average, BelowAverage and Poor--> </systemroute> <systemroute> <sourcesystemname>meridio System B</sourceSystemName> <!-- The name of the second system (System B).--> <connectionstring>timeout=100000;dmwsuri= meridiodmws.asmx;rmwsuri= ;RUWSURI= vices=false</connectionstring> <!--The location of the web services for System A.--> <connectionspeed>excellent</connectionspeed> <!-- A user defined value to describe the connection quality between the machine defined in sourcesystemname and systemname. Values can be Excellent, VeryGood, Good, Average, BelowAverage and Poor--> </systemroute> </systemroutes> 5. For each system that you want to connect to (e.g. System B), add the following. The first <systemroute> must define the system on which Meridio for Microsoft SharePoint is installed (System A); the second <systemroute> must define the system itself (System B). Subsequent <systemroute> sections can be added. Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 128

136 <system> <systemname>meridio System B</systemName> <!--The name of the Meridio system --> <location>some Town</location> <!--Some location information.--> <comment>head Office, Human Resources</comment> <!--A comment to help users understand what the system is used for.--> <contactname>mr. Smith</contactName> <!--A contact name should a problem arise.--> <contact address>contact address@test.com</contact address> <!--An address for the contact person.--> <systemroutes> <!--The SystemRoutes collection is used to determine the best web services to use when connecting the system defined above from another system.--> <systemroute> <sourcesystemname>meridio System A</sourceSystemName> <!-- The name of the system on which Meridio for Microsoft SharePoint is installed (System A).--> <connectionstring>timeout=100000;dmwsuri= meridiodmws.asmx;rmwsuri= ;RUWSURI= vices=false</connectionstring> <!--The location of the web services for System B.--> <connectionspeed>excellent</connectionspeed> <!-- A user defined value to describe the connection quality between the machine defined in sourcesystemname and systemname. Values can be Excellent, VeryGood, Good, Average, BelowAverage and Poor--> </systemroute> <systemroute> <sourcesystemname>meridio System B</sourceSystemName> <!-- The name of the second system (System B).--> <connectionstring>timeout=100000;dmwsuri= meridiodmws.asmx;rmwsuri= ;RUWSURI= vices=false</connectionstring> <!--The location of the web services for System B.--> <connectionspeed>excellent</connectionspeed> <!-- A user defined value to describe the connection quality between the machine defined in sourcesystemname and systemname. Values can be Excellent, VeryGood, Good, Average, BelowAverage and Poor--> </systemroute> </systemroutes> </system> Chapter 18 - Meridio for Microsoft SharePoint Configuration Settings 129

137 CHAPTER 19 Initial System Configuration Tasks This chapter explains some of the system administration tasks that should be performed after installing a new Meridio system. In particular, System Administration Tasks (see page 132) includes a checklist of tasks which must be completed before the system can be used to store documents. Network Configuration If the system is using RPC over HTTP, direct binding may be used to connect a client application directly to a particular Meridio system by using direct binding. If you change a Meridio Server s computer name, domain or IP Address after installing the Server, you need to stop and restart the Meridio Server service. This updates network information in the Meridio Database. Security Issues To securely protect all documents in a Meridio system, the following Windows security requirements must be satisfied: Meridio should only use NTFS partitions. The Meridio Server, Meridio Storage Agent, Meridio Scheduler and IDOL content search services should all run under the same Windows user. This user should be the same as the user that was used to install Meridio, and should only be used for activities that relate to Meridio. See Domain Users Configuration on page 20. Versions and Renditions folders should have NTFS permissions whereby the only Windows users to have access to these folders are the user that is used to run the Meridio services, and the users who perform manual backups and restores. These users should have Full control. Configuration To enable the Meridio Server to send , the Meridio Server must be able to contact an IIS SMTP service. Refer to the documentation for IIS for details on how to set up the SMTP service. To set up configuration for each Meridio system: Use Meridio Administration to launch the System Properties dialog box for the required Meridio system and select the Configuration tab. Select the appropriate address type, e.g. SMTP, and apply the change. Chapter 19 - Initial System Configuration Tasks 130

138 To enable the use of URLs in a Meridio system: 1. Use Meridio Administration to invoke the System Properties dialog box for the required Meridio system and select the and URL tab. Select the type of URL that the system will support and enter the relevant information: Select Meridio Protocol to generate URLs suitable for use with Meridio Protocol Handler. Enter the URLs for Meridio for Web Users and Meridio for Microsoft SharePoint. Select Meridio for Web Users to support URLs that are suitable for use with Meridio for Web Users. Enter the name of the web server on which Meridio for Web Users is running. Select Custom to support custom URLs. Enter the name of the web server and the URL template. 2. Apply the changes. This enables users to send document links as URLs when accessing a Meridio system through a Web interface. To set up configuration for individual users: For each user wishing to use the facility (either directly, or indirectly through the search agents), use Meridio Administration to update their User Properties with their address. Meridio on SQL Server 2005 Microsoft SQL Server 2005 selectively installs and starts key services and features to reduce the attackable surface area of a system. In the default configuration of new installations, many features are not enabled. A system administrator can change these defaults at installation time and also selectively enable or disable features of a running instance of SQL Server Some default settings introduced during new SQL Server 2005 installations have an impact on Meridio functionality and require further configuration after Meridio Server is installed. Enabling SQL Mail Stored Procedures For new SQL Server 2005 installations, SQL mail stored procedures are disabled by default. These must be enabled as Meridio functionality currently supports the sending and receiving of messages from the database engine. To enable SQL mail support: 1. Launch the SQL Server Surface Areas Configuration tool (Start All Programs Microsoft SQL Server 2005 Configuration Tools SQL Server Surface Area Configuration). 2. Click Surface Area Configuration for Features. Chapter 19 - Initial System Configuration Tasks 131

139 3. Select the SQL Mail node and select Enable SQL Mail stored procedures. 4. Click Apply. System Administration Tasks If you are installing a new Meridio system, complete the following checklist of actions to ensure that the system is properly configured: If you are using multiple Content Servers, or a database-only installation, the Backup folder created on installation of a Meridio Content Server (default path C:\Meridio\Server\Backup) should be shared on your Windows domain, with the share name Kbackup. This is so that Content Servers that are not on the same machine as the Meridio Database can access the database dump file when carrying out a backup or restore. Ensure that the Meridio server can contact the IIS SMTP service, on either the Meridio server machine or another machine on the local network, from which to send messages. Make sure that your server machine is configured to run with a 24-hour clock. If you are using multiple Content and Application Servers, all Server clocks must be synchronised. Set the date format in your Regional Settings (available from the Windows Control Panel) to use 4 digits for the year. This is necessary to avoid a problem with the SQL Server date format, and also to deal with Y2K issues. The Meridio Server, Meridio Scheduler, and Meridio Storage Agent services should be configured with a user s account and password. This user must be a member of the Windows Administrators group on the Meridio Server machine (in particular, it must have the Log on as a service user right). This should automatically be carried out at installation, provided a valid password was entered. If you need to make changes Chapter 19 - Initial System Configuration Tasks 132

140 to a service s startup settings, remember to stop and restart the service for the changes to take effect. The amount of memory dedicated to SQL Server is dynamically configured. We recommend that this is set to a fixed size, appropriate to the total amount of memory available on the machine. You can do this by updating the Configuration Options for Memory in the SQL Enterprise Manager. By default, Microsoft SQL Server uses the Named Pipes network protocol. However, it may perform better using the TCP/IP protocol. To install TCP/IP network support for SQL: 1. Rerun the SQL Setup program. 2. In the list of installation options, select Change Network Support. 3. Select the TCP/IP Sockets check box under Install/Uninstall Networks. To have SQL Server use TCP/IP as the default protocol, run the SQL Server Client Configuration utility, go to the Net Library tab, and select TCP/IP Sockets in the Default Network list box. Before any documents can be added to the system, a partition must be registered. You can do this using the Add Partition wizard in Meridio Administration. See Chapter 4, Storage Management of Meridio for System Administrators. Ensure that all the partitions visible to Windows are formatted as NTFS (recommended) or FAT. The Add Partition wizard can only display partitions that have been formatted, and an error is logged in the Windows Application Event Log for each unformatted partition found. A system administrator user is pre-configured when the Meridio Server is installed. The name of the user is Admin and the case-sensitive password is Admin. Immediately update this password from the User Properties dialog box for the Admin user in Meridio Administration. Similarly, a user responsible for managing keyword hierarchies is also pre-configured; this user is named Keywords and its initial password Keywords should be updated. See Chapter 5, Users, Groups and Access Control of Meridio for System Administrators. Create the required users and groups for the Meridio system using the Add User and Add Group wizards. If there are large numbers of users or groups to be added it is recommended that you create templates to record all the common properties and then use the Bulk Add wizard. All of these wizards are accessed via Meridio Administration see Chapter 5, Users, Groups and Access Control of Meridio for System Administrators. If you intend to use the LDAP Directory Synchronisation task (see Meridio LDAP Synchronisation Task Administration Guide), you should create a Meridio user which the LDAP Synchronisation task will use to log in to Meridio when bulk-adding users and groups. The user should have the same name (User Name) as the Windows account used by the Meridio Scheduler service, and should be a member of the Admin group. Create a Default Access List for the system and Default Access Lists for each user as required. You can do this using the Meridio Administration System Properties and User Properties dialog boxes respectively. See Chapter 3, Getting Started with Meridio Administration, and Chapter 5, Users, Groups and Access Control of Meridio for System Administrators. Chapter 19 - Initial System Configuration Tasks 133

141 CHAPTER 20 Upgrading Meridio This chapter details how to upgrade a Meridio system by upgrading its Meridio database, content servers and application servers. It also details how to upgrade Meridio for Microsoft SharePoint. Upgrading Meridio Server If you have an earlier version of Meridio Server installed, you can upgrade it to the latest version. It is possible to upgrade a restricted installation of a Meridio Server (such as Meridio Developer, or a previous evaluation version) to Meridio Full, subject to the purchase of appropriate licences. For more information, please contact support@meridio.com. Meridio 2.2 Servers Meridio 2.2 SR-6 (version ) and 2.2 SR-7 (version ) servers must be upgraded to Meridio 5.1 in several stages: 2.2 -> 2.3 -> 2.3 SR-1 -> 3.0 -> 5.1 The Meridio 2.2 server must be running on SQL Server 7.0 or MSDE. Meridio 2.3 does not support SQL Server 6.5. Therefore a Meridio 2.2 Server using SQL Server 6.5 for the Meridio Database cannot be upgraded directly to Meridio 2.3. If you are using SQL Server 6.5, support@meridio.com for assistance in migrating your current SQL Server 6.5 database to SQL Server 7.0, in preparation for supporting release 2.3. If the Meridio 2.3 Server installer reports that Setup has detected a previous installation on your machine that cannot be upgraded directly to 2.3. and you are sure that you are trying to upgrade a 2.2 release, then support@meridio.com with details of the following registry key value: HKEY_LOCAL_MACHINE/SOFTWARE/Kainos/Meridio Server. Meridio 2.3 Servers Meridio 2.3 (version ) and 2.3 SR-1 (version ) servers must be upgraded to Meridio 5.1 in several stages: 2.3 -> 2.3 SR-1 -> 3.0 -> 5.1 Meridio 3.0 Servers Meridio 3.0 (version ), 3.0 SR-1 (version ), 3.0 SR-2 (version ) and 3.0 SR- 3 (version ) servers may be upgraded directly to Meridio 5.1. Meridio 3.1 Servers Meridio 3.1 (version 3.1.2) servers may be upgraded directly to Meridio 5.1. Chapter 20 - Upgrading Meridio 134

142 Meridio 3.2 Servers Meridio 3.2 (version ) servers may be upgraded directly to Meridio 5.1. Meridio 3.3 Servers Meridio 3.3 (version ), 3.3 SR-1 (version ) and 3.3 SR-2 (version ) servers may be upgraded directly to Meridio 5.1. Meridio 4.0 Servers Meridio 4.0 (version ) servers may be upgraded directly to Meridio 5.1. Meridio 4.1 Servers Meridio 4.1 (version ) and 4.1 SR-1 (version ) servers may be upgraded directly to Meridio 5.1. Meridio 4.2 Servers Meridio 4.2 (version ), 4.2 SR-1 (version ) and 4.2 SR-2 (version ) servers may be upgraded directly to Meridio 5.1. Meridio 4.3 Servers Meridio 4.3 (version ) and 4.3 SR-1 (version ) servers may be upgraded directly to Meridio 5.1. Meridio 4.4 Servers Meridio 4.4 (version ), 4.4 SR-1 (version ) and 4.4 SR-2 (version ) servers may be upgraded directly to Meridio 5.1. Meridio 5.0 Servers Meridio 5.0 (version ) and 5.0 SR-1 (version ) servers may be upgraded directly to Meridio 5.1. Performing the Upgrade In a multi-server setup, computers must be upgraded in the same order as they were installed, one at a time. This means that a Meridio Database with or without a Content/Application Server should be upgraded first, followed by any separate Content Servers and then by any separate Application Servers. All separate Content and Application Servers must be stopped (using the Windows Services Control Manager) before the upgrade process begins, as they cannot communicate properly with an upgraded Database until they have also been upgraded. If previously revoked, the System Administrators role must be restored for both the meridiodatabaseuser and for the DMSUser SQL credentials. To upgrade a Meridio Server installation: Note: Steps 1-5 and 7-13 apply to all Meridio upgrades; however, Step 6 applies only to upgrading Meridio 2.2 to 2.3, and Step 11 applies only to upgrading from a pre-3.2 Content Server. 1. Determine the Server configuration currently installed by identifying the machines where the Meridio Database, Content Server(s) and Application Server(s) reside. Chapter 20 - Upgrading Meridio 135

143 2. Perform a full backup of the entire Meridio system including the Meridio Web Services web.config files. Note any Meridio virtual directory configuration settings. If you use LDAP Directory Synchronisation in Meridio to import users and groups from Active Directory, a copy of the kldap.ini (located by default in C:\Meridio\Server\Bin) must be saved. 3. Uninstall all Meridio Clients residing on machines that are part of the server configuration. 4. Use the Services Control Manager in the Windows Control Panel to stop the Meridio Server services on all Content and Application Servers. 5. Run the latest Meridio Server installer on the machine that houses the Meridio Database. This is the machine that has one of the following configurations: Database only Content Server and Database Application Server and Database If the machine has a content or application server then during the installer s execution you are asked whether the server s existing Meridio Eventhooks DLL should be overwritten with the newer version on the CD. You may be using a customised version of this DLL for use with the Meridio Server s event hooks. If you wish to retain the existing software, answer No to the query. 6. Run the Meridio Data Migration utility (only applies to upgrading Meridio 2.2 to 2.3). During the 2.3 upgrade of the database, a separate Meridio Data Migration utility is launched and migrates any custom properties to the new Meridio Database schema. Chapter 20 - Upgrading Meridio 136

144 Select a machine on which to upgrade the Meridio Server. All machines in your Windows domain are listed by network name, not Meridio system name or Meridio Server name so ensure that you select a machine that has a Meridio Server installed. Click OK, enter the system administrator (sa) password for SQL Server, and then click Start on the main utility dialog box. When the migration has finished, click Close. Depending on the amount of data to migrate, this utility may take some time to complete. You can choose to proceed with the migration now or postpone it until later. If you decide to run the utility later, it is essential that you do not resume using Meridio until the custom property data has been migrated. The Meridio Data Migration utility (MigrateApp.exe) is copied to the Meridio\Server\bin folder on every Content Server and can be run by double-clicking the icon. Check that no errors are logged by the utility; otherwise there may be problems using the upgraded Meridio Database. You should avoid creating global custom properties or version custom properties if you have upgraded your Meridio Server to 2.3, or above, and are still running Meridio 2.2 client applications against it. Global custom properties and the association of version custom properties with document categories are new features for Meridio 2.3, which are not supported by 2.2 clients. 7. Reboot the upgraded Meridio Database machine. 8. Run the latest Meridio Server installer on any separate Content Servers. As in step 5, you are asked whether the existing Meridio Eventhooks DLL should be overwritten. If the DMSDB database is installed on a named SQL instance, verify that the ODBC System DSN created by the upgrade accurately specifies the Server\Instance for the value of the Server setting. 9. On one of the Content Server machines, run the Add Users to IDOL utility (from Start Programs Meridio Server) to synchronise Meridio users with those configured for content searching. 10. Reboot each upgraded Content Server machine. You should avoid creating global custom properties or version custom properties if you have upgraded your Meridio Server to 2.3, or above, and are still running Meridio 2.2 client applications against it. Global custom properties and the association of version custom properties with document categories are new features for Meridio 2.3, which are not supported by 2.2 clients. 11. The format of the Content Search Indexes changed in Meridio 3.2. If you upgrade a Content Server from a pre-3.2 version, it is necessary to run the Content Search Upgrade from the Start Programs Meridio Server group after the server upgrade is complete. You must run this upgrade on each upgraded Content Server machine. If this utility is not run, content searching of old and new documents will not be available. The old content search index files is deleted by the upgrade, therefore ensure that you have an up-to-date backup before upgrading. Chapter 20 - Upgrading Meridio 137

145 On startup, the utility displays the location of the index directory, the number of documents currently indexed in the index, and the number of documents waiting to be indexed. The upgrade consists of several steps: deleting the old content search index files, updating the database to cause all indexed documents to be re-indexed, creating the new index files, then re-indexing existing indexed documents in batches. As each batch of documents is re-indexed, the display of the number of documents indexed and the number waiting to be indexed is updated. 12. Click Start Upgrade to start the upgrade. Upgrades need to be carefully planned, since this utility may take some time to complete, depending on the number of documents to be indexed. Contact for advice before proceeding. It is possible to cancel the upgrade by pressing Cancel Upgrade. Cancellation does not take effect immediately, only when the utility is changing from one upgrade step to another, or when it is about to re-index the next batch of documents. A cancelled upgrade may be continued later the utility continues from the point at which it was previously cancelled. 13. Run the latest Meridio Server installer on any separate Application Servers. As in point 5 above, you are asked whether the existing Meridio Eventhooks DLL should be overwritten. 14. Reboot each upgraded Application Server machine. If the server does not start correctly after the Application Server machine is rebooted, a second reboot is required. 15. Run the latest Meridio SOAP Server installer on any Meridio SOAP Servers. Modify the MeridioSOAP virtual directory configuration settings to match those that existed before the upgrade, for example, for timeouts, unified login and application pool. Ensure that Domain Users are granted both Read and Write access to the C:\Meridio\SOAP\MeridioSOAP\HtmlConversion folder. 16. Run the latest Meridio Web Services installer on any Meridio Web Servers. For each Meridio Web Services virtual directory, modify the configuration settings to match those that existed before the upgrade, for example, for timeouts, unified login and application pool. Ensure that each virtual directory has been created as an application. Also for each Meridio Web Services virtual directory, compare the upgrade s web.config files to its backup copy, and update the upgraded web.config files to match any modified settings in the backup. Be careful to merge the updates into the new web.config files; do not copy the backup copy over the new web.config. After upgrading, documents are re-indexed; this may take some time and may affect the results of a search. Chapter 20 - Upgrading Meridio 138

146 If you use LDAP Directory Synchronisation in Meridio to import users and groups from Active Directory, then the saved kldap.ini file must be copied into C:\Meridio\Server\Bin (the default location). If you are upgrading from a pre-4.4 Meridio installation, updates to kldap.ini may be required. See Meridio LDAP Directory Synchronisation Task Administration Guide for more information. If system-wide default views exist for Meridio for Microsoft Outlook, these are destroyed when Meridio is upgraded. Upgrading Meridio for Microsoft SharePoint 2003 An existing 4.1, 4.2, 4.3, 4.4 or 5.0 installation of Meridio for Microsoft SharePoint 2003 can be upgraded to 5.1. If upgrading from a version of Meridio for Microsoft SharePoint earlier than 4.3, you must first upgrade to Meridio for Microsoft SharePoint 4.3 before upgrading to version 5.1. All Meridio client software must be uninstalled, and the Meridio Server must be upgraded before upgrading Meridio for Microsoft SharePoint If you are upgrading from Meridio 4.3 or earlier and use smart shortcuts, the Smart Shortcut Update utility must be run to update the shortcuts to the newer Meridio version. See To run the Smart Shortcut Update utility on page 140 for details. To upgrade Meridio for Microsoft SharePoint 2003: 1. Run the installation for Meridio 5.0 SR-1 for Microsoft SharePoint. The existing version will be detected; click Yes to continue. 2. The Destination Location page is displayed, on which you need to select a path where Meridio for Microsoft SharePoint is installed. You can accept the default path C:\Meridio\SharePoint, or browse for a different path by clicking Browse. Note that if the Meridio for Microsoft SharePoint search protocol handler is to be installed, the drive chosen must be an NTFS drive. 3. On the Use Remote Content Server page, select whether you wish the Meridio for Web Users application to use a Meridio Remote Content Server for document content retrievals. If you selected Yes, an additional page is displayed asking for the name of the machine running the Meridio Remote Content Server. A list of web sites on the machine is displayed. Select those sites which are to be updated as part of the installation of the client software. 4. On the Determine Meridio Replication Status page, select whether the system is part of a replication group. 5. If the previous installation included the Meridio for Microsoft SharePoint search protocol handler, three more screens are displayed: i. Enter the name of the Meridio system whose content is to be searched. Chapter 20 - Upgrading Meridio 139

147 ii. Enter the account details of a Meridio user to be used to retrieve records from the Meridio system for indexing by SharePoint. This user must have Read access to all of the documents, fileplans and records that you wish to index. This means that you must assign protective markings to the user if you use protective markings on the fileplan structure and wish the items within the fileplan to be indexed. iii. Enter the name of the default domain to be used for searches. When mapping Meridio user names to domain users, the default domain is the first domain in which Windows accounts are looked for. If there are Meridio users or groups that don t have equivalent accounts, the security model will not be mapped completely, which can cause incorrect access rights. 6. The Start Copying Files page displays the information that you entered in the previous steps, for confirmation. It also shows both the amount of disk space required for the various parts of the installation, and the amount of space available in each case. You cannot continue unless the space requirements are met. However, if there is not enough space available on the current drive for the installation to take place, or you notice that some of the details entered are incorrect, you can click Back to return to the previous pages in the wizard where you can browse to select a destination path that has more free space or change other information. 7. When you are satisfied that the information is correct, click Next to complete the installation. All application files are copied to the installation directory. A progress bar and displayed messages indicate the progress of the installation. 8. Once the files have been copied, a Thank You page is displayed. Click Finish to exit the wizard. If you do not wish to view the README file, then clear the check box. 9. After the installation is complete, restart the IIS Admin service. To run the Smart Shortcut Update utility: 1. Log in to the machine where the Meridio for Microsoft SharePoint 2003 files are installed, as a user with full write permissions for any SharePoint sites, document libraries and lists which may be updated by the utility. 2. From the location of the SharePoint files (e.g. C:\Meridio\SharePoint), run the following in a command prompt: MeridioSPUtil /server SharePointServer /MeridioSystem MeridioSystem /WebServiceURL WebServiceURL /action SmartShortcutUpdate Additional, optional parameters can be used. The following table describes all available parameters. Parameter Required Description /server SharePointServer Yes SharePointServeris the name of the SharePoint server. Chapter 20 - Upgrading Meridio 140

148 Parameter Required Description /MeridioSystem MeridioSystem /WebServiceURL WebServiceURL /action SmartShortcutUpdate Yes Yes Yes MeridioSystem is the name of the Meridio system. WebServiceURL is the URL of the Meridio DM Web Service (DMWS), e.g. The action for the utility it must be SmartShortcutUpdate for this process. /port Port No The port of the SharePoint server. If this is not supplied, the default is 80. /site SiteName No SiteName is the site on which the upgrade is run. If this is not supplied, all sites on the SharePoint server are processed. /list DocumentLibrary No DocumentLibrary is the document library on which the upgrade is run. If this is not supplied, all document libraries found are processed. /output level Level No Level is the log level of the action: 5 displays all sites, all document libraries and all files, and whether they were updated. 4 displays all sites, document libraries and files that have been updated; this is the default value. 3 displays all sites, document libraries and files that have been updated but does not display the individual URLs of files. 2 displays all sites and document libraries which have been updated, and displays the number of smart shortcuts updated. 1 displays when the process begins, how many smart shortcuts are updated, and when the process ends. 3. When prompted, enter a username and password of an account in the specified Meridio system. The account must have full access to any Meridio items updated by the utility. If errors occur, the update process continues where possible. Any smart shortcuts which have been updated are not processed again if the utility is re-run. Chapter 20 - Upgrading Meridio 141

149 Upgrading Meridio for Microsoft SharePoint 2007 To upgrade a Meridio for Microsoft SharePoint 2007 installation, follow the recommended uninstallation procedure (see page 89), and then install the new version of Meridio for Microsoft SharePoint 2007 (see page 80). Upgrading Meridio for Microsoft SharePoint 2003 to Meridio for Microsoft SharePoint 2007 A server running Microsoft SharePoint 2003 with Meridio (version 4.4 or later) can be upgraded to Microsoft SharePoint 2007 without losing the Meridio configuration. Meridio for Microsoft SharePoint 2003 remains available throughout most of the upgrade process. There are two methods of performing this upgrade: gradual both the Microsoft SharePoint 2003 and 2007 installations are on the same server or server farm (see page 142) content migration the Microsoft SharePoint 2003 and 2007 installations are on separate servers or server farms (see page 145) Familiarity with administering Microsoft SharePoint 2003 and 2007 is assumed. Refer to the Microsoft documentation where directed in the following procedures, for further information and upgrade steps. It is assumed for the following procedures that all Microsoft SharePoint and Meridio installations have been installed to the default locations. Amend file locations as necessary if this is not the case. Gradual Upgrades The following procedures describe how to upgrade the Meridio for Microsoft SharePoint customisation for a single web site (web application) only. If you have other SharePoint customisations, upgrade them according to Microsoft documentation. See After Upgrading on page 145 for information about upgrading further Meridio for Microsoft SharePoint web sites. Before Upgrading During the following procedure, refer to the Microsoft documentation where directed. Before upgrading Microsoft SharePoint, perform the following steps: 1. Ensure that the current deployment of Microsoft SharePoint 2003, including Meridio, is working correctly. 2. Upgrade other Meridio components, such as Meridio Server, to version 5.0 SR-1 as necessary. 3. Backup and verify the SharePoint SQL databases. 4. Install WSS 2.0 Service Pack 2 and Microsoft SharePoint 2003 Service Pack 2, if not already installed. Chapter 20 - Upgrading Meridio 142

150 5. Ensure that all IIS virtual servers have the same service packs applied. 6. Refer to the Microsoft documentation for any additional steps. 7. Install Microsoft.NET Framework Refer to the Microsoft documentation for any additional steps. Running a Gradual Upgrade During the following procedure, refer to the Microsoft documentation where directed. 1. Install MOSS When prompted, select to perform a gradual upgrade as shown in the following illustration. 2. Refer to the Microsoft documentation for any additional steps. 3. When prompted, do not run the Configuration Wizard. 4. Run prescan.exe /all from a command prompt to generate reports about the Microsoft SharePoint 2003 installation prescan.exe is located by default in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin. These reports may include errors about the Meridio STS file definitions no action is necessary. Refer to the Microsoft documentation for further information. 5. Delete the MeridioSharePoint.cab wppack by running the following from a command prompt: C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\bin\stsadm -o deletewppack -name MeridioSharePoint.cab Chapter 20 - Upgrading Meridio 143