eroom 7 Indexing Server Advanced Installation only November 2004

Transcription

1 Advanced Installation only November 2004

2 Copyright Documentum, a division of EMC. All Rights Reserved. DOCUMENTUM, NOW YOU KNOW, UNITING THE WORLD THROUGH CONTENT and the Corporate Logo are trademarks or registered trademarks of Documentum, a division of EMC, in the United States and throughout the world. All other company and product names are used for identification purposes only and may be trademarks of their respective owners. 2 of 5

3 Overview Indexing is a background task that runs on an indexing server and is managed by the eroom Scheduler service. The Scheduler indexes the content of all files in eroom so they are included in eroom searches. eroom Advanced installation is a multi-server application, in which the web server, indexing server, database server, and file server typically reside on different machines. In contrast, eroom Standard installation embeds the index engine in the eroom web server installation (and indexes are stored on the web server in the default c:\eroom data directory). Audience This document is intended to guide eroom administrators in installing and administering the indexing server for an eroom 7 Advanced installation. It covers these topics: Requirements and preparation Upgrade considerations When to install the indexing server Installing the indexing server Administering the indexing server Other indexing server considerations For more information For additional eroom architecture information, refer to the eroom 7 Architecture White Paper, eroom 7 Capacity Planning paper, or eroom Installation, Upgrade, and Configuration Guide. Requirements and preparation Installing an indexing server requires Windows 2000 or 2003 operating system. Single-, dual-, or quad-processor machines are all acceptable hardware for the indexing server. While it is possible to install the eroom 7 indexing server on the database server or the web server, it is recommended that you install it either on a separate server, or on the file server itself. Do not install the indexing server on the Real Time Server. Note: Clustering of the indexing server installation is currently not supported. 3 of 5

4 Before you install the eroom indexing server, consider these factors at your site: Security policies - Enable the Local Security Policy can logon as a batch job and logon locally for the File Share User on the indexing server. Indexing port - All eroom servers communicate with the indexing server on port 2060, by default. This is configurable via the eroom MMC snap-in by right-clicking on the indexing server. All indexing servers on the site must use the same port. Indexing servers access the file servers directly using the prevailing file access protocols. This port is required for communication during site creation (during installation) or upgrades, and is required for normal use of eroom, since eroom data is indexed continually. File server ports - The indexing server uses NETBIOS and CIFS ports (137, 138, 139, 445) to communicate with the file store. Upgrade considerations Unlike a Standard-to-Standard upgrade, an eroom Standard-to-Advanced installation upgrade requires a new, separate install of the eroom indexing server. After the upgrade, an indexing server from the old installation appears in the eroom MMC snap-in for the upgraded site. Install and add the new indexing server and remove the old one. When upgrading the eroom 7 web server, first upgrade the indexing server to the same version, since the indexing server should be available and running during the web server upgrade. When to install the indexing server Installing the indexing server before you run the eroom 7 Advanced installation setup program can save you time because: When the eroom site creation wizard asks for it, you will already have the machine name or IP address of the indexing server. You won t have to add the indexing server to the site later (using the eroom MMC snap-in). You can install the indexing server after the eroom 7 installation, however. In this case, just skip the step in the site creation wizard that asks for the name of the indexing server, and use the MMC to add it later. The site creation wizard can complete without the name of the indexing server. Installing the indexing server The indexing server setup program is located on the Documentum download site with the eroom 7 files, and is called eroom 7 Search Engine Installation. The index installation executable should be the same version as the eroom web server. 1. Download, unzip, and run the indexing server setup program on the machine you want to use as an indexing server. The InstallShield wizard opens. 2. Choose the directory for the indexing program files. 3. Choose a data directory folder. Change the default (c:\eroom data\) to a drive location with sufficient disk space to contain the full text index files for each facility. 4 of 5

5 4. Specify the fileshare user account as domain\user. If you are not installing the indexing server in a Windows Domain, you can specify the local server on which you created the fileshare user as server\user. 5. Confirm and agree to the installation settings. The installation continues until finished. The eroom 7 indexing server setup program installs Hummingbird indexing services (both the Hummingbird Connector Service and Hummingbird STR Service). Administering the indexing server Once it is installed, the eroom 7 indexing server requires minimal administration. Indexing runs every five minutes by default, and is configurable in the eroom MMC snap-in by right-clicking eroom Server and picking Server Tuning. eroom 7 creates one full-text index per facility. Indexing can be enabled or disabled for the entire site on the Scheduler page of Site Settings. Site administrators (or community administrators with rebuild facility indices permission) can rebuild indexes for individual facilities using the rebuild index button on the General page of Facility Settings (which you access via the Facilities page of Community Settings). Indexes can be backed up along with eroom data. However, the index may not accurately correspond to the facility data depending on the timing of the backup and restore. In the event the indexing server fails, indexes can always be rebuilt. Other indexing server considerations Adding indexing servers to the eroom 7 site. New indexing servers can be added by installing the second indexing server and then adding that indexing server to the eroom 7 site on the web server Site Admin console. Indexing errors. eroom displays errors in the Windows server event log. eroom also creates a FailedOperation.csv file in the data directory you specify for the index files. Additionally,.log files are created within the same directory for each index eroom maintains. Lastly, etrace is the most useful utility to diagnose indexing problems. Enable the etrace settings for Full Text Index at 5 and recreate the indexing problem. Technical support may request the etrace, Windows event logs,.csv file, and.log files when troubleshooting indexing issues. Content Server integration. An eroom file that is linked to the Content Server is indexed like any other eroom file. The physical linked file is stored in the Content Server, but is indexed in both eroom and the Content Server. From an end user's point of view, searching the eroom or the site level works exactly the same whether the eroom file is linked to the content server or stored in eroom. Note that in eroom 7, the eroom application does not cache the linked file on the eroom web server. Instead, eroom retrieves the file from the Content Server every time it needs to be indexed. 5 of 5

6 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United State and other countries. All other trademarks used herein are the property of their respective owners.