imanage WorkSite Server Installation Guide

(1)

iManage WorkSite

Server Installation Guide

Version 8.5

(2)

Notice

No part of this publication (hardcopy or electronic form) may be reproduced or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Autonomy Corporation plc and its affiliates. Information in this manual is furnished under license by Autonomy Corporation plc and its affiliates and may only be used in accordance with the terms of the license agreement. If this software or documentation directs you to copy materials, you must first have permission from the copyright owner of the materials to avoid violating the law which could result in damages or other remedies.

Trademarks and Copyrights

Interwoven, iManage, ConfirmSite, ContentServices, ControlHub, DataDeploy, DeskSite, FileSite, iManage, iManage Universal Search, iManage WorkSite, LiveSite, MediaBin, MetaCode, MetaTagger, OffSite, OpenDeploy, Primera, Records Manager, iManage Records Manager, Scrittura, TeamPortal, TeamSite, VisualAnnotate, WorkDocs, WorkPortal, WorkRoute, WorkSite, WorkSite Express Search, WorkTeam, the respective taglines, logos and service marks are trademarks of Autonomy Corporation plc and its affiliates, which may be registered in certain jurisdictions. All other trademarks are owned by their respective owners. Some or all of the information contained herein may be protected by patent numbers: US # 6,505,212, GBRI # 1053523, US # 6,480,944, US# 5,845,270, US #5,430,812, US #5,754,704, US #5,347,600, AUS #735365, AU 7830068, GB #GB2333619, US #5,845,067, US #6,675,299, US #5,835,037, AUS #632333, CAN #2,062,965, FRAN / GRBI / SPAI / SWED #480941, GERM #69020564.3, KORS 10-0576487, JAPA #2968582, MX #219522, NZ #516340, SING #109524, SG #89006, SG #89086, SG #74973, SG #85502 US #5,065,447, US #6,609,184, US #6,141,017, US #5,990,950, US #5,821,999, US #5,805,217, US #5,838,832, US #5,867,221, US #5,923,376, US #6,434,273, US #5,867,603, US #4,941,193, US #5,822,721, US #5,923,785, US #5,982,938, US #5,790,131, US #5,721,543, US #5,982,441, US #5,857,036, US #6,697,532, US #6,792, 454, US #6,928,149, US #7,092,969 or other patents pending application for Autonomy Corporation plc and its affiliates.

Autonomy Corporation plc Cambridge Business Park Cowley Rd Cambridge CB4 0WZ Tel: +44 (0) 1223 448000 Fax: +44 (0) 1223 448001 Email: [email protected] Copyright Notice

(3)

About This Book

9

Intended Audience. . . 9 Notation Conventions . . . 9 Manual Organization . . . 11 Product Documentation . . . 11 Revision History . . . 12 Documentation Updates . . . 12

Chapter 1:

Preliminary Setup

13

Overview . . . 13

Creating a Domain Account for WorkSite Server . . . 13

Adding the User to the Administrators Group . . . 14

Configuring Accounts for Use as Services . . . 15

File Server Setup . . . 16

Creating a Windows File Server . . . 16

Configuring a Shared Drive in Windows 2008 . . . 17

Configuring a Shared Drive in Windows 2003 . . . 18

Creating a Novell NetWare File Server . . . 19

SQL Server Installation and Setup. . . 19

Recommended Drive Configuration . . . 20

Installing Microsoft SQL Server . . . 20

Configuring SQL Server and Creating the WorkSite Database . . . 21

Chapter 2:

Installing WorkSite Server

27

Preparing for the WorkSite Server Installation . . . 27

Creating an ODBC System Data Source. . . 27

Testing Connectivity. . . 34

Installing WorkSite Server. . . 35

Prerequisites . . . 35

Recommendations . . . 35

Adjusting Virtual Memory Size. . . 35

Changing the Default Temp Directory Environmental Variables . . . 36

Configuring Network Adapter Settings . . . 36

Running the WorkSite Server Installer . . . 37

(4)

Contents

Installing Novell NetWare Client . . . 39

Upgrading WorkSite Server. . . 39

Chapter 3:

Creating the WorkSite Tables

43

Prerequisites . . . 43

Initializing the Database . . . 43

Troubleshooting the Initialization Process . . . 46

Chapter 4:

Setting Up WorkSite Services

47

Overview . . . 47

Registering WorkSite Server Service . . . 47

Step 2: Connect WorkSite Server Service to Databases . . . 49

Selecting the Databases to Which the WorkSite Server Should Connect . . . 49

Step 3: Configure Connections from WorkSite Server to File Servers . . . 51

Step 4: Start WorkSite Server Service . . . 53

Step 5: Check the WorkSite Server Service Log File . . . 53

Chapter 5:

Testing Connectivity and Final Tasks

55

Testing Connectivity . . . 55

Step 1: Add a Test User . . . 55

Step 2: Install and Run a WorkSite Client . . . 55

Step 3: Import a Document. . . 56

Additional Tasks . . . 56

Appendix A: Recommended SQL Maintenance Tasks and Scheduled Dumps

59

Overview . . . 59

Recommended Maintenance Plans . . . 60

Creating a Maintenance Plan for WorkSite Databases. . . 60

Configuring the Check Database Integrity Task . . . 66

Configuring the Rebuild Index Task. . . 70

Configuring the Update Statistics Task. . . 73

Configuring the Back Up Database (Full) Task . . . 76

Configuring the Back Up Database (Transaction Log) Task . . . 79

Completing the Maintenance Plan . . . 82

Appendix B: Installation Record

87

(5)

•

Figures

Figure 1 Select Users... 14

Figure 2 Local Security Policy Setting Dialog ... 15

Figure 3 Select Users or Groups Dialog ... 16

Figure 4 Configuring a Shared Folder in Windows 2008 Server... 17

Figure 5 Connect to SQL Server Dialog... 21

Figure 6 SQL Server Management Studio ... 22

Figure 7 Tempdb Properties - tempdev File Initial Size ... 23

Figure 8 New Database Dialog ... 24

Figure 9 Database File Location ... 25

Figure 10 ODBC Data Source Administrator, System DSN tab... 28

Figure 11 Create a New Data Source to SQL Server Dialog ... 29

Figure 12 Create a New Data Source to SQL Server, Login ID Verification Dialog... 30

Figure 13 Create a New Data Source to SQL Server, Default Database Dialog ... 31

Figure 14 Create a New Data Source to SQL Server, Language Settings Dialog ... 32

Figure 15 ODBC Microsoft SQL Server Setup Summary ... 33

Figure 16 Tests Completed Successfully Dialog... 34

Figure 17 Network Card Properties - Advanced Tab ... 36

Figure 18 WorkSite Service Add/Remove Dialog ... 38

Figure 19 WorkSite Server Startup Dialog ... 38

Figure 20 Register/Unregister Databases... 44

Figure 21 Logon to Database... 44

Figure 22 Select Default File Server Type ... 45

Figure 23 Default Document File Server Information... 46

Figure 24 WorkSite Server Startup Dialog ... 48

Figure 25 Database Setup Dialog ... 49

Figure 26 Database Properties Dialog for WorkSite Server Service... 50

Figure 27 ODBC Source(s) Dialog... 50

Figure 28 File Server Connections Dialog, Windows tab... 52

Figure 29 File Server Connections Dialog, NetWare Tab ... 53

Figure 30 Excerpt from Normal WorkSite Server Service startup messages ... 54

Figure 31 Login to WorkSite Server Dialog... 56

Figure 32 SQL Server Management Studio ... 61

Figure 33 SQL Server Maintainence Plan wizard ... 62

Figure 34 Select Plan Properties ... 63

Figure 35 Select Maintenance Tasks... 64

Figure 36 Select Maintenance Task Order ... 65

Figure 37 Define Database Check Integrity Task ... 66

(6)

Figures

Figure 39 Defining Database Check Integrity task... 68

Figure 40 Job scheduling for Database Integrity check ... 69

Figure 41 Configured database integrity task ... 70

Figure 42 Configuring the rebuild index task... 71

Figure 43 Job scheduling for rebuilding the index task ... 72

Figure 44 Updated rebuild index task window ... 73

Figure 45 Defining the update statistics task ... 74

Figure 46 Job schedule for updating statistics ... 75

Figure 47 Defining the update statistics task ... 76

Figure 48 Configuring the back up database (full) task... 77

Figure 49 Job schedule for Back Up Database (full)... 78

Figure 50 Updated Define Back Up Database (Full) Task window ... 79

Figure 51 Define Back Up Database (Transaction Log) Task page... 80

Figure 52 Job Schedule Properties dialog box ... 81

Figure 53 Updated Back Up Database (Transaction Log) task... 82

Figure 54 Select Report Options page... 83

Figure 55 Complete the Wizard page ... 84

(7)

Tables

Table 1 Notation Conventions... 9

Table 2 Revision History ... 12

Table 3 SQL Collation Settings for Additional Language Support ... 26

(8)

(9)

About This Book

This guide provides detailed instructions for installing the WorkSite Server and WorkSite Server with Caching and the accompanying components of the WorkSite Document Management System (DMS).

This guide should be used in conjunction with the WorkSite Server Overview and Planning

Guide, which presents several design scenarios for planning and implementing WorkSite in your

organization.

For detailed information about WorkSite Server utilities and services, refer to the WorkSite

Server Administrator’s Guide.

For all information about WorkSite Indexer, refer to the WorkSite Indexer Administrator’s

Guide.

Intended Audience

This guide is intended for system administrators who will install the WorkSite Server.

Notation Conventions

This manual uses the following notation conventions:

Table 1 Notation Conventions

Convention Definition and Usage

Bold Text that appears in a GUI element such as, a menu item, button, or element of a dialog box, and command names are shown in bold. For example:

(10)

About This Book

This guide also uses the following conventions:

The term “Windows” indicates any supported version of the Microsoft Windows operating system, such as Windows®_2003.

Directory paths use UNIX conventions. These conventions mandate using forward slashes (/ ) in path names. (Windows systems use backward slashes.) The Windows convention is used when referring to a Windows-specific directory. For example:

UNIX: docroot/news/front.html Windows: docroot\news\front.html

Italic Book titles appear in italics.

Terms are italicized the first time they are introduced. Important information may be italicized for emphasis. Monospace Commands, command-line output, and file names are in

monospace type. For example:

The iwextattr command-line tool allows you to set and look up extended attributes on a file.

Monospaced

italic Monospaced italics are used for command-line variables.For example: iwckrole role user

This means that you must replace role and user with your values.

Monospaced bold Monospaced bold represents information you enter in response to system prompts. The character that appears before a line of user input represents the command prompt, and should not be typed. For example:

iwextattr -s project=proj1 //IWSERVER/default/main/dev/ WORKAREA/andre/products/index.html

Monospaced bold

italic Monospaced bold italic text is used to indicate a variable in user _{input. For example:} iwextattr -s project=projectname workareavpath

means that you must insert the values of projectname and workareavpath when you enter this command.

[] Square brackets surrounding a command-line argument mean that the argument is optional.

| Vertical bars separating command-line arguments mean that only one of the arguments can be used.

Table 1 Notation Conventions

(11)

Manual Organization

This manual is organized as follows:

Chapter 1, “Preliminary Setup,” includes instructions for setting up a domain account for all WorkSite services, as well as the file server, SQL Server and databases.

Chapter 2, “Installing WorkSite Server,” describes how to configure the WorkSite

Middle-tier Server prior to installing the WorkSite software. It also includes instructions for installing DMS Server Software.

Chapter 3, “Creating the WorkSite Tables,” describes how to create a WorkSite database. Chapter 4, “Setting Up WorkSite Services,” provides instructions for configuring the

WorkSite Server Service to connect to your WorkSite databases.

Chapter 5, “Testing Connectivity and Final Tasks,” includes information about testing your WorkSite installation, and completing miscellaneous tasks.

Appendix A, “Recommended SQL Maintenance Tasks and Scheduled Dumps,” contains instructions for scheduling and performing recommended maintenance tasks on your WorkSite SQL database.

Appendix B, “Installation Record,” includes a form where you can record information about your WorkSite installation.

Product Documentation

The following documents are also available with the WorkSite Server and WorkSite Server with Caching:

WorkSite Server Administrator’s Guide WorkSite Server Design Guide

WorkSite Indexer Administrator’s Guide WorkSite Server online help

(12)

About This Book

Revision History

Refer to Table 2 for a list of updates to this guide.

Table 2 Revision History

Revision Date Comments

1 August 2007 8.2 SP1 Release. 2 December 2007 8.3 Release.

• Updated information regarding the new 8.3 WorkSite Indexer in Chapter 10, “Installing and Configuring WorkSite Indexer.”

• Added configuration information for Symantec Enterprise Vault.

3 December 2007 • Minor corrections to Chapter 10, “Installing and Configuring WorkSite Indexer.”

4 July 2008 8.3 Patch 2 Release.

• Updates to Chapter 10, “Installing and Configuring WorkSite Indexer.”

• Minor changes to Symantec Vault Integration section.

5 September 2008 8.3 SP1 Release.

• Removed Chapter 10, “Installing and Configuring WorkSite Indexer.”

All information about WorkSite Indexer is now contained in the WorkSite Indexer Administrator’s

Guide which is new for the 8.3 SP1 release.

• Removed information about configuring Symantec Vault Integration. This information is now located in the WorkSite Server Administrator’s Guide.

• Removed information for configuring the Rules Engine service. This information is now located in the WorkSite Server Administrator’s Guide.

6 April 2009 8.5

• Updated Appendix A, “Recommended SQL Maintenance Tasks and Scheduled Dumps”.

(13)

Chapter 1

Preliminary Setup

Overview

This chapter contains information about the preliminary setup for the various components of the WorkSite system.

Creating a Domain Account for WorkSite Server

File Server Setup

SQL Server Installation and Setup

Creating a Domain Account for WorkSite

Server

A number of WorkSite Server processes run as services and must be configured to start under the context of a valid administrator account.

Autonomy recommends creating a new domain user, such as worksite_admin, which will be used to operate all WorkSite Server related services. This WorkSite Administrator account will be used to start all WorkSite services, and authenticate with the SQL Server databases and file servers.

Perform the following steps before continuing:

1. On the Windows domain controller, create a WorkSite Administrator domain user account. Check the Password never expires option.

(14)

Chapter 1: Preliminary Setup

2. On each server where WorkSite will be installed, add this WorkSite Administrator account to the membership of the local Administrators group. Refer to “Adding the User to the Administrators Group” on page 14 for detailed instructions.

3. Confirm that the WorkSite Administrator account (or the local Administrators group) has the following privileges granted on all servers (using the Local Security Policy snap-in): Act as part of the operating system

Log on as a service.

Refer to “Configuring Accounts for Use as Services” on page 15 for detailed instructions. 4. Configure this account with read and write access to the network attached storage or file

server location where all of the WorkSite documents will be stored. No other accounts need (or should have) access to the WorkSite documents.

Adding the User to the Administrators Group

For each Windows server which will have WorkSite Server installed, add the WorkSite Administrator user account to the Administrators group:

1. Right-click My Computer and select Manage to open the Computer Management Console. 2. Expand the Local Users and Groups and select Groups.

3. Double-click Administrators to open the Administrators Properties dialog. 4. Click Add to open the Select Users or Groups Dialog.

(15)

Creating a Domain Account for WorkSite Server

Configuring Accounts for Use as Services

To grant Log on as a service and Act as part of the operating system privileges for the WorkSite Administrator user account:

1. On each server where WorkSite Server will be installed, start the Local Security Settings console.

Start -> All Programs -> Administrative Tools -> Local Security Policy 2. Expand Local Policies, and select User Rights Assignments.

3. Double-click Log on as a service. The Local Security Policy Setting dialog opens.

Figure 2 Local Security Policy Setting Dialog

(16)

Figure 3 Select Users or Groups Dialog

5. Enter the WorkSite Administrator user account you created in “Adding the User to the Administrators Group” on page 14, and click OK.

6. Double-click Act as a part of the operating system. The Local Security Policy Setting dialog opens.

7. Click Add User or Group. The Select Users or Groups dialog opens.

8. Enter the WorkSite Administrator user account you created in “Adding the User to the Administrators Group” on page 14, and click OK.

9. Click OK to exit Local Security Policy Setting dialog.

Perform these steps on each Windows server where WorkSite Server will be installed.

File Server Setup

This section provides instructions for creating a Windows or Novell Netware file server where the WorkSite Server will store WorkSite documents. Only the user account running the

WorkSite Server service should have access to this file server.

(17)

File Server Setup

2. For Windows Server 2003, add the File Server role using the Windows Manage Your Server Administrative Tool.

3. Proceed to Configuring a Shared Drive in Windows 2008 or Configuring a Shared Drive in Windows 2003.

Configuring a Shared Drive in Windows 2008

1. In Windows 2008 Server, open the Server Manager.

Click Start, then click Control Panel, then Administrative Tools, and then click Manage

Your Server. The Manage Your Server page opens.

2. Expand the Roles node, then expand the File Services node. Click the Share and Storage

Management, as shown in Figure 4.

Figure 4 Configuring a Shared Folder in Windows 2008 Server

3. On the right side of the Server Manager, click Provision Share and follow the prompts in the wizard.

4. On the NTFS Settings page, select the Yes, change NTFS permissions options, then click

Edit Permissions and define the following permissions for this shared folder:

a. In the Permissions dialog, add the WorkSite domain user (worksite_admin) that you configured in “Creating a Domain Account for WorkSite Server” on page 13. Allow the following permissions for this user:

• Modify

• Read & Execute • List Folder Contents • Read

(18)

b. Remove all other groups or user names from the list. No other users or groups should have access to the WorkSite file server share.

c. Click OK.

5. Proceed through the wizard to the SMB Permissions page. Select the Users and groups

have custom share permissions option, then click Permissions to edit the permission

settings.

a. In the Permissions dialog, add the WorkSite domain user (worksite_admin) that you configured in “Creating a Domain Account for WorkSite Server” on page 13. Allow the following permissions for this user:

• Full Control

c. Click OK.

6. Proceed through the remainder of the wizard selecting the default options. 7. Click Create to complete the file share setup.

Configuring a Shared Drive in Windows 2003

1. In Windows 2003 Server, open the Server Manager.

Click Start, then click Control Panel, then Administrative Tools, and then click Manage

Your Server. The Manage Your Server page opens.

2. Under the File Server section, click Add shared folders. The Share a Folder wizard opens. 3. On the Folder Path page, enter the location of the shared folder where WorkSite documents

will be stored, then click Next.

4. Enter a name for this shared folder, then click Next.

5. On the Permissions page, select Use custom share and folder permissions, then click

Customize. The Customize Permissions dialog opens.

a. On the Share Permissions tab, add the WorkSite domain user (worksite_admin) that you configured in “Creating a Domain Account for WorkSite Server” on page 13. Allow the following permissions for this user:

• Full Control

(19)

d. Add the WorkSite domain user (worksite_admin) that you configured in “Creating a Domain Account for WorkSite Server” on page 13. Allow the following permissions for this user:

• Modify

• Read & Execute • List Folder Contents • Read

• Write

e. Remove all other groups or user names from the list. No other users or groups should have access to the WorkSite file server share.

f. Click OK.

6. Click Finish to complete the Share a Folder Wizard.

Creating a Novell NetWare File Server

1. Create a new shared directory on the file server that will be used to store WorkSite

documents. The sample directory name “IDOCS” is used throughout the documentation to refer to the file server shared directory.

Record the name of this directory on your Installation Record.

2. Grant supervisory access to this directory for the user that will run the WorkSite Server service. No other users or groups need to have access to this directory.

SQL Server Installation and Setup

The chapter provides instructions for Microsoft SQL Server.

Before you begin the installation of Microsoft SQL Server, we strongly recommend that you read the Installing SQL Server book, which is in the Microsoft SQL Server software package. This book is also available if you install Microsoft SQL Server Books Online as part of the SQL Server installation.

As you install SQL Server, list all your information in Appendix B, “Installation Record.” It will assist technical support if you need help later.

(20)

Recommended Drive Configuration

Autonomy recommends creating two logical drives on the SQL Server. The C:\ drive should contain the operating system. The D:\ drive should contain everything else, including backup software and the database server software. Autonomy recommends a RAID 10 disk

configuration with a minimum of 10GB of space dedicated for databases. For more information, refer to the WorkSite Server Design Guide.

Installing Microsoft SQL Server

See the WorkSite Supported Platforms document for a list of supported versions of Microsoft SQL Server.

The user account used to run the SQL Server installer must have administrative rights on the server. See “Adding the User to the Administrators Group” on page 14 for detailed instructions. Confirm that Microsoft Data Access Components (MDAC) 2.8 or higher is installed on all the server where SQL Server will be installed. Starting with Windows 2003 Server, this software component is included in all Windows Service Packs.

1. Log in as the WorkSite Administrator domain user you created in “Creating a Domain Account for WorkSite Server” on page 13.

2. Insert the SQL Server CD-ROM into your server. The installer should automatically start. If necessary, double-click Autorun.exe on the CD to start the installer.

3. Follow the onscreen instructions to start the installer.

4. On the Components to Install screen, select (at a minimum) SQL Server Database Services. 5. On the Service Account screen, select Use a domain user account, and enter the

information of the WorkSite Server administrator account that you created earlier.

This allows the SQL Server process to run using the same account as the WorkSite Server process.

6. On the Authentication Mode screen, select Windows Authentication Mode.

NOTE

If you have chosen not to create a WorkSite Administrator domain account, you must select Mixed Mode instead.

(21)

Configuring SQL Server and Creating the WorkSite Database

This section describes the necessary steps for configuring SQL Server to support WorkSite databases, as well as the steps to create an new (empty) WorkSite database.

NOTE

To support additional languages, you must define the SQL Server collation as described in

step 7.

1. On the server where SQL Server was just installed, launch the SQL Server Management Studio.

Start | All Programs | Microsoft SQL Server 2008 | SQL Server Management Studio

or

Start | All Programs | Microsoft SQL Server 2005 | SQL Server Management Studio

The Connect to Server dialog opens.

Figure 5 Connect to SQL Server Dialog

2. In the Server name field, enter the name of the database server, then click Connect. The Microsoft SQL Server Management Studio opens, as shown in Figure 6:

(22)

Figure 6 SQL Server Management Studio

Increasing the Size of the TEMPDB Database

SQL Server comes with a tempdb database that is used to store temporary tables to facilitate sorting and manipulation of large data sets. The default size of 8MB of this database must be increased to support WorkSite.

To increase the size of the tempdb database:

1. In the SQL Server tree, expand the Databases folder. 2. Expand the System Databases folder.

3. Right-click the tempdb database and select Properties. The tempdb Properties dialog opens.

4. Select the Files page.

(23)

Figure 7 Tempdb Properties - tempdev File Initial Size

6. Click OK.

Creating the WorkSite Database in SQL Server

1. In the SQL Server Management Studio window, right-click the Databases folder and select

(24)

Figure 8 New Database Dialog

2. In the Database name field, enter the name for the WorkSite database. 3. To change the default location of the database data and log files:

a. In the list of database files, locate the new database data file.

(25)

Figure 9 Database File Location

c. In the list of database files, locate the log file for this database. d. In the Path column, enter the new location for the transaction logs.

This should be the same path as the data file.

4. Use the formula below to determine the appropriate starting size for the data file and enter that value in the Initial Size (MB) field of the data file.

(Estimated Maximum Number of Documents x 5) / 1024 = ________

NOTE

The initial size of the Data Device must be at least 500 MB. If you are importing documents from an external source and are expecting a larger initial size, increase the initial size to a larger value, such as 1024 MB.

5. Use the formula below to determine the appropriate starting size for the log file and enter that value in the Initial Size (MB) field of the log file

Initial Size of Data File in MB / 5 = ______

6. To support a non-english language in the WorkSite database, select Options in the New Database dialog.

7. In the Collation field, specify the collation of the database. This setting determines how strings of character data are sorted and compared, and varies across languages and locales. If you are setting up a multi-language WorkSite Server, you must pick a SQL Collation that matches your language.

A list of certified SQL Collations options is provided in Table 3.

The Locale ID must also be entered on all WorkSite Servers which connect to this database. This value is defined in the Service Manager after installing and starting WorkSite Server.

(26)

Refer to “Configuring WorkSite Server Service Properties” in the Chapter 2 of the WorkSite

Server Administrator’s Guide.

Table 3 SQL Collation Settings for Additional Language Support

Language Locale ID SQL Collation

Chinese (simplified) 2052 Chinese_PRC_CI_AS

English 1033 SQL_Latin1_General_CP1_CI_AS French 1036 French_CI_AS German 1031 Latin1_General_CI_AS Hebrew 1037 Hebrew_CI_AS Italian 1040 Latin1_General_CI_AS Japanese 1041 Japanese_CI_AS Polish 1045 Polish_CI_AS Russian 1049 Cyrillic_General_CI_AS

(27)

Chapter 2

Installing WorkSite Server

This chapter contains the following information: Preparing for the WorkSite Server Installation

Installing WorkSite Server Upgrading WorkSite Server

NOTE

To configure the WorkSite Server as a cluster using the optional WorkSite Clustering Service, refer to the WorkSite Server Administrator’s Guide.

Preparing for the WorkSite Server Installation

The following steps must be performed before installing the WorkSite Server:

Configure SQL Component/Client Settings

Create an ODBC Connection to the SQL Server database

Before starting the installation, verify that the version of Microsoft Windows installed on your server is supported by WorkSite. Refer to the WorkSite Supported Platforms document for a complete list of supported operating systems.

Creating an ODBC System Data Source

Each WorkSite Server must have a data source connection established with the WorkSite database.

(28)

Chapter 2: Installing WorkSite Server

To create this data source:

1. Open the ODBC Data Source Administrative utility.

From the Windows Start menu, point to Administrative Tools, and then click Data Sources

(ODBC).

NOTE

If you are installing WorkSite Server on a 64-bit version of Windows Server, you must use the 32-bit ODBC Source Administrator tool. Open the 32-bit version located at C:\

Windows\SysWOW64\odbcad32.exe.

2. Click the System DSN tab.

Figure 10 ODBC Data Source Administrator, System DSN tab

3. Click Add to display the Create New Data Source dialog box.

4. Highlight SQL Server in the list of installed ODBC drivers, and then click Finish. The Create a New Data Source to SQL Server dialog opens, as shown:

(29)

Preparing for the WorkSite Server Installation

Figure 11 Create a New Data Source to SQL Server Dialog

5. In the Name field, enter the name of the WorkSite database that you created on the SQL Server in Chapter 1, “Preliminary Setup.”

The data source name should not exceed 8 characters and should not contain characters other than letters and numbers. Letters should be either all upper case or all lower case; do not mix cases.

The data source name will be the name of the database as it appears to WorkSite users. 6. In the Server field, enter the name of the SQL Server.

7. Click Next. The next screen displays options for authenticating to the SQL Server, as shown:

(30)

Figure 12 Create a New Data Source to SQL Server, Login ID Verification Dialog

8. Select SQL Server authentication and enter the SQL Server Login ID and Password. 9. Select the Connect to SQL Server to obtain default settings option.

10. Click Next.

11. In the Change the default database to field, select the database that you created earlier in this chapter, as shown in Figure 13.

(31)

Figure 13 Create a New Data Source to SQL Server, Default Database Dialog

12. Select both Use ANSI quoted identifiers and Use ANSI nulls, paddings and warnings. These settings are required for saved searches when using UUEncode (All language support with the indexer).

13. Click Next to continue.

14. If you require multi-language support, then uncheck the Perform translation for character

(32)

Figure 14 Create a New Data Source to SQL Server, Language Settings Dialog

(33)

Figure 15 ODBC Microsoft SQL Server Setup Summary

(34)

Figure 16 Tests Completed Successfully Dialog

If all information was correct, you will see the message, “TESTS COMPLETED SUCCESSFULLY”.

The test connection might fail if you have unchecked the Perform translation for character

data option but the ODBC connection is successful and is fully functional.

17. Click OK to close the message dialog.

18. Click OK to close the Setup Summary dialog.

19. Click OK to close the ODBC Data Source Administrator dialog.

Testing Connectivity

The following tests will verify connectivity at the most basic level (network level), then at the level of the native networking protocol for SQL (using ISQL), and at the level of ODBC connectivity (using ODBCAD32.EXE).

(35)

Installing WorkSite Server

where servername is the name of your SQL Server.

2. A successful ping will return the IP Address of the SQL Server.

Installing WorkSite Server

Prerequisites

Before starting the WorkSite Server installation, verify that:

All Windows Critical and Recommended Updates have been applied to all the servers where WorkSite Server is to be installed. You can download the required patches from Microsoft. If the Novell NetWare Client is installed on the server, it must be uninstalled before

beginning the WorkSite Server installation.

Recommendations

Adjusting Virtual Memory Size

To make the most efficient use of the server hardware, configure the virtual memory (page file) to be twice the amount of RAM available on each of the WorkSite servers. For example, if the server has 2GB of RAM, set the virtual memory size to 4GB. The page file should reside on a local drive and not on a shared disk or SAN volume.

To configure the virtual memory settings:

1. Right-click My Computer and select Properties. 2. Select the Advanced tab.

3. In the Performance section, click Settings. 4. Click the Advanced tab.

5. In the Virtual memory section, click Change.

6. Adjust the Maximum size (MB) to twice the amount of physical RAM installed on this server. Note that 4GB is the maximum allowed.

(36)

Changing the Default Temp Directory Environmental Variables

By default, Windows defines separate temp directories for the user and the system. WorkSite Server makes use of both of these temp directories. As a best practice, configure both the system and user environmental variables to point to the same directory, such as D:\Temp\WorkSite\. To access the Environmental Variables dialog, right-click My Computer and select Properties. On the Advanced tab, click Environmental Variables.

Configuring Network Adapter Settings

Set the Network Speed Manually

On all WorkSite servers, the network card settings should be set manually to static speeds that match the LAN or WAN configuration (for example,100 Mbps/Full Duplex as shown in

Figure 17). For most network cards, this setting is known as Link Speed & Duplex or Media Type.

(37)

Installing WorkSite Server

To access the network adapter properties dialog, open the Windows Device Manager, and expand the Network adapters node. Right-click the name of the network card and select

Properties. The configuration parameters are located on the Advanced tab.

Disable DHCP Media-sense

In addition, since the server must be configured with a fixed IP address, disable DHCP media-sense by adding the following registry value to each WorkSite server.

In the following location in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters Add or modify the following DWORD value:

DisableDHCPMediaSense: 1

Running the WorkSite Server Installer

The installation instructions are the same for WorkSite Server and WorkSite Server with Caching. Autonomy recommends executing the installation while logged in as the account used to start the service. This practice ensures the proper registration of all components.

If you are upgrading an existing installation, refer to “Upgrading WorkSite Server” on page 39. To install using the command line, or to install in silent mode, refer to “Installing WorkSite Server in Silent Mode” on page 39.

To install WorkSite Server or WorkSite Server with Caching:

1. Log into the server using the WorkSite Server administrator domain account that was created earlier.

2. Run the WorkSite Server or WorkSite Server with Caching setup.exe file located on the installation CD, and follow the instructions in the installation wizard.

3. Click Finish when the installation is complete.

4. After installation, the WorkSite Service Add/Remove dialog opens. Add the WorkSite Server service by selecting it in the left column, then clicking Add.

(38)

Figure 18 WorkSite Service Add/Remove Dialog

When you add the WorkSite Server or Rules Engine, WorkSite prompts you to enter the startup information for each service, as shown in Figure 19. These services use the Login ID and Password for the Windows User Account.

(39)

Upgrading WorkSite Server

5. Enter the account information for the WorkSite Server administrator domain user that you created earlier.

6. Under Startup Type, select Automatic to start the service automatically after Windows is restarted.

7. Click OK.

NOTE

WorkSite services can be added or removed at any time by running the imSvcIns.exe

program.

8. Restart your server to complete the installation of WorkSite Server.

Installing WorkSite Server in Silent Mode

To install WorkSite Server in silent mode, use the following command line syntax: Setup.exe /s /v" /qn SERIALNUMBER="<serial number>"

OR

MsiExec.exe /i "<path to Full_Installer/*.msi file>" /qn SERIALNUMBER="<serial number>"

Installing Novell NetWare Client

After installing the WorkSite Server, install the latest supported version of the NetWare Client for Windows. The NetWare Client must be installed for the WorkSite Server to access to the Novell file server or directory.

Upgrading WorkSite Server

Upgrading existing installations of the WorkSite software suite requires planning, especially when servers are configured to connect to databases in multiple offices. WorkSite Server 8.5 can connect to databases with schemas that have been upgraded to version 8.2 SP1, but it cannot connect to databases with older schemas.You must upgrade the database server software to use the new features introduced in WorkSite 8.5.

For more information on upgrading to WorkSite Server 8.5 and it’s related components, see the

(40)

For more information about supported database server software, see the WorkSite 8.5 Limited

Release Supported Platforms data sheet.

NOTE

Make a backup of all databases as well as the Server installation directory before performing the upgrade.

To upgrade an existing installation of WorkSite Server: 1. Stop all WorkSite Services.

2. Document all WorkSite Server service settings before uninstalling.

3. Uninstall the existing WorkSite Server. The new installer will check for, and remove, previous versions of the server software, however performing a manual uninstall is recommended.

4. Install the new WorkSite Server software. See “Installing WorkSite Server” on page 35. When the installation is complete, the WorkSite Service Add/Remove dialog opens. 5. Unregister and then register the WorkSite services:

Remove WorkSite services that appear in the Installed box. They are now listed in the Available box.

Add the services in the Available box back into the Installed box.

NOTE

You can perform this step even after the installation program has exited by running the WorkSite Service Installer program (imSvcIns.exe), which is available in the WorkSite Server installation directory.

6. Run the Service Manager and connect the WorkSite Service to the appropriate databases. Configure database properties, if necessary.

7. Confirm that all options are configured properly in the Service Manager. 8. Start the WorkSite Service from the Service Manager.

9. Review the log file to confirm that the WorkSite Server service has successfully connected to all databases and file servers. The following excerpt from the WorkSite Server log file indicates a successful connection to the Sales database:

Thu 05/31 17:39:58.421 Pool: 557:Info[1164] Connected to database Colorado Thu 05/31 17:39:58.578 FileServer: 226:Info[1164] Connected to file server

(41)

Upgrading WorkSite Server

10. Run DeskSite or FileSite from a client workstation to verify that you can connect to the server.

11. Perform the following tasks to confirm that you have established full connectivity with the WorkSite Server:

Perform Trusted Login to the WorkSite Server Perform a profile search

Quickview documents Import a document

(42)

(43)

Chapter 3

Creating the WorkSite Tables

This chapter describes how to create the WorkSite tables in your empty database.

Prerequisites

Before you can create your WorkSite database, you must: Create the directory to store the documents

Install and configure the SQL Server Install WorkSite Server

Initializing the Database

After you create an empty database using the tools provided by the database vendor and register the database as an ODBC data source, you need to initialize the database as a WorkSite

database. This is accomplished using the Database Administration program that was installed with your WorkSite Server Software. The Database Administration program installs WorkSite tables in the SQL database.

1. Run the Database Administration program on the WorkSite Server.

From the Windows Start menu, point to All Programs, then Autonomy Server, then click

Database Administration.

2. From the Database menu, select Register/Unregister. The Register/Unregister Databases dialog opens.

(44)

Chapter 3: Creating the WorkSite Tables

Figure 20 Register/Unregister Databases

3. Any databases that you have registered as ODBC data sources on the computer as described in “Creating an ODBC System Data Source” on page 27 should appear in the Register/ Unregister Databases list on the left.

Select the name of the database and click Register. The Logon to Database dialog opens.

Figure 21 Logon to Database

4. Enter the login ID and password for the SQL Server Administrative account and click OK. The login ID for this account is always “sa.”

(45)

Initializing the Database

Figure 22 Select Default File Server Type

6. Select the operating system type for the Default File Server and click Next.

The Default File Server is the server where documents will be stored for users who are not assigned to another file server.

7. Select how documents should be organized on the File Server in the Path Creation Options box, as shown in Figure 23.

Select Default to store documents according to Author information.

Select Path based on Custom1 Entry to store documents according to Custom1 metadata information.

(46)

Chapter 3: Creating the WorkSite Tables

Figure 23 Default Document File Server Information

8. In the Path field, enter the full path to the shared directory that you created earlier on the File Server for storing the documents. Click the Browse button (...) to select from a list of available locations.

NOTE

If the file server’s operating system type is Novell NDS, enter the Container Name in the Server Context field and the machine name and path to the directory in the Path field. 9. Click Next, and then click Finish to install the WorkSite tables in the database.

A message dialog “WorkSite Tables Created Successfully” appears when the process is complete.

10. Click OK to return to the Register/Unregister Databases dialog, and click Close to return to the WorkSite Database Management application.

Troubleshooting the Initialization Process

If you experience any difficulty creating a WorkSite Database using the Create WorkSite Database dialog box, consult Chapter 3 of the WorkSite Server Administrator’s Guide. You can also contact Autonomy Technical Support. Have the DBADMIN.LOG file ready for review. You

(47)

Chapter 4

Setting Up WorkSite Services

Overview

After you have used the Database Administration program to install WorkSite tables in your SQL database, you need to configure WorkSite Server Service to connect to this database. This stage of the installation process involves these steps:

Register WorkSite Server Service with the Service Manager Configure which databases will be served by the WorkSite Server Connect WorkSite Server Service to your WorkSite database

You can run WorkSite Service Manager on Windows 2008 only if you are a part of the Administrator's group on the local machine.

Registering WorkSite Server Service

To Register WorkSite Server Service with the Service Manager: 1. Run the WorkSite Service Manager.

2. Click the Register Server button or select Register Server from the Service

pull-down menu. The Select Server dialog box appears. The keyboard shortcut for Register Server is Ctrl-R.

3. In the Select Server dialog box, type the server name in the Server text-entry field or click the icon for the server that you want to register.

4. After you select a server to register, click OK in the Select Server dialog box. If the WorkSite Service Manager connects with the WorkSite Server Service, Index Services, WorkKnowledge Services, or Rules Engine Service programs successfully, entries for these programs appear in the main table view.

(48)

Chapter 4: Setting Up WorkSite Services

NOTE

If you did not configure startup properties during installation, configure them now using the Service Manager.

Configure Startup Properties for a Service

1. Highlight the WorkSite Server Service in the main table view.

2. Click the button in the toolbar or select Startup Properties from the Service pull-down menu. The WorkSite Server Startup dialog box appears.

Figure 24 WorkSite Server Startup Dialog

3. Enter the Login ID and Password for the Windows User account under whose context the WorkSite Server Service program will run. This account must be different from the

Windows service account Local System and must have “Log on as a service” privileges. The default value that appears in the Login ID field in the Startup dialog box is that of the current user.

(49)

Overview

Step 2: Connect WorkSite Server Service to Databases

You can connect each WorkSite Server to multiple WorkSite Databases. If multiple services are running on the same machine, the different WorkSite service programs can connect different sets of databases.

Selecting the Databases to Which the WorkSite Server Should Connect

1. Highlight the service in the main program window.

2. Click the Database button in the toolbar. The Database Setup dialog box for that service appears.

Figure 25 Database Setup Dialog

The Database Setup dialog box shows those databases that the WorkSite Server is currently serving. If you have not connected WorkSite Server Service to any databases yet, the list view in this dialog box is blank.

Adding a connection to a database

(50)

Figure 26 Database Properties Dialog for WorkSite Server Service

2. Enter a database name in the Database text-entry box or click the browse button to select a database from those already defined as ODBC data sources. When you click the browse button, the ODBC Source(s) dialog box appears.

NOTE

It is always a best practice to use the browse button to locate a database rather than entering the database name.

The ODBC Source(s) dialog box lists all ODBC data sources defined on your local machine.

Figure 27 ODBC Source(s) Dialog

(51)

Overview

3. Enter the SQL Administrative Login ID and Password that the Server will use to log into the database. This ID and password must have system administrator-level access to the database (that is, the SA account).

4. If this database will function as a Primary Database for this WorkSite Server, check the

Primary Database checkbox. Primary Databases are the default sources for WorkSite

Forms for the server. (For more information on Primary Databases, see Chapter 2 of the

WorkSite Server Administrator’s Guide.)

5. If you want to maintain a 1:1 ratio of threads to connections for this database, keep the As

many connections as threads checkbox checked. Otherwise, clear this box and enter a

custom number of SQL connections that the WorkSite Server should maintain to this database. The ratio of threads to connections can be customized per database. (For more information on this option, see Chapter 2 of the WorkSite Server Administrator’s Guide.)

NOTE

For information about configuring the WorkSite Indexer portion of this dialog, refer to the

WorkSite Indexer Administration Guide.

6. Click OK to add the database to the list of those being served by the WorkSite Middle-tier Server.

Step 3: Configure Connections from WorkSite Server to File

Servers

The File Server Connections dialog is used to enter login information for the accounts which will be used by the WorkSite Server Service to access the document file server(s).

By default, the WorkSite Server uses the Windows account that was used to log in to access to the file server. To specify an alternative account to use.

For Windows File Servers

To configure connections between WorkSite Server and a Windows file server: 1. In the WorkSite Service Manager, select the WorkSite Server Service.

2. From the Properties menu, select File Server Setup or click the File Server Setup icon. The File Server Connections dialog opens.

(52)

Figure 28 File Server Connections Dialog, Windows tab

4. Disable the Use Service Logon only option.

5. Enter a valid Windows domain Login ID and Password which has access to the file server. 6. Click OK.

7. Stop and restart the WorkSite Server service.

For NetWare File Servers

To configure connections between WorkSite Server and a NetWare file server: 1. In the WorkSite Service Manager, select the WorkSite Server Service.

2. From the Properties menu, select File Server Setup or click the File Server Setup icon. The File Server Connections dialog opens.

(53)

Overview

Figure 29 File Server Connections Dialog, NetWare Tab

3. Select either a Bindery or NDS connection.

4. Enter the LoginID and Password for the Novell NetWare User Account created for the WorkSite Middle-tier Server or Indexing Server.

5. If you selected NDS, then you must also enter a Context. 6. Click OK.

7. Stop and restart the WorkSite Server service.

Step 4: Start WorkSite Server Service

Highlight WorkSite Server Service, then click Start to start WorkSite Server Service. If you have any problem starting WorkSite Server Service, check all of the settings created for

WorkSite Server Service in this chapter and check the WorkSite Server Service Log File (below) for clarifying information.

Step 5: Check the WorkSite Server Service Log File

Whether or not you have any problem starting WorkSite Server Service, check the WorkSite Server Service Log File to verify that WorkSite Server Service is running and connected to the database. To see the WorkSite Server Service Log File, highlight WorkSite Server Service and click Log View.

(54)

If WorkSite Server Service is running properly, you should see a series of log file entries similar to the following:

Figure 30 Excerpt from Normal WorkSite Server Service startup messages

Wed 02/06 17:40:34.195 RegistryMap: 536:Header [1804] Registry value: LogonID - ************************************ Wed 02/06 17:40:34.195 RegistryMap: 536:Header [1804] Registry value: Password -

************************************

Wed 02/06 17:40:34.195 Pool: 557:Info [1804] Connected to database CODYPARK

Wed 02/06 17:40:35.406 FileServer: 226:Info [1804] Connected to file server path \\BOWEN2\IMANINDEX for CODYPARK:IDXSERVER

Wed 02/06 17:40:35.406 FileServer: 226:Info [1804] Connected to file server path \\BOWEN2\IMANDOCS for CODYPARK:DEFSERVER

Wed 02/06 17:40:35.497 Pool: 557:Info [1804] Connected to database CODYPARK

Wed 02/06 17:40:35.597 Pool: 545:Header [1804] DB: COLORADO - Driver: SQLSRV32.DLL - Version: 3.80.194

Wed 02/06 17:40:35.597 Pool: 548:Header [1804] DB: COLORADO - DBMS: Microsoft SQL Server - Version: 8.0.194 Wed 02/06 17:40:35.597 RegistryMap: 536:Header [1804] Registry value: LogonID - ************************************ Wed 02/06 17:40:35.597 RegistryMap: 536:Header [1804] Registry value: Password -

************************************

WWed 02/06 17:40:35.597 Pool: 557:Info [1804] Connected to database COLORADO

Wed 02/06 17:40:35.877 FileServer: 226:Info [1804] Connected to file server path \\BOWEN2\IMANINDEX for COLORADO:IDXSERVER

Wed 02/06 17:40:35.877 FileServer: 226:Info [1804] Connected to file server path \\BOWEN2\IMANDOCS for COLORADO:DEFSERVER

Wed 02/06 17:40:35.977 Pool: 557:Info [1804] Connected to database COLORADO

Wed 02/06 17:41:00.262 Connection: 97:Info [1988] CON 2140980: Connected to full-text index - COLORADO.

Wed 02/06 17:41:00.993 Connection: 97:Info [1988] CON AF0E40: Connected to full-text index - CODYPARK.

(55)

Chapter 5

Testing Connectivity and Final

Tasks

Testing Connectivity

After you have WorkSite Server Service running, perform the following tests to ensure that the WorkSite Client can connect to the database.

Step 1: Add a Test User

1. Run the Database Administration program on the WorkSite Server.

From the Windows Start menu, point to All Programs, then Autonomy Server, then click

Database Administration.

2. Select the User node, then right-click in the right pane and select Add. The Add New Users dialog opens.

3. Enter a User ID (such as TESTUSER) and Password for this user, then click Add.

Step 2: Install and Run a WorkSite Client

1. Install a WorkSite Client (DeskSite or FileSite) on a computer with network access to the WorkSite Server.

(56)

Chapter 5: Testing Connectivity and Final Tasks

Figure 31 Login to WorkSite Server Dialog

Step 3: Import a Document

Log into the WorkSite database with your TESTUSER account. Import a document to the database.

If you can connect to WorkSite and import a document, you have successfully installed WorkSite Server.

Additional Tasks

After you have successfully installed WorkSite Server, you can install maintenance scripts, and fine tune WorkSite Server and Database performance. You can also customize the appearance and behavior of the client. See the WorkSite Server Administrator’s Guide for information about related administrative tools.

You also need to complete the following optional tasks:

Add the group NRTADMIN to the database. You must be a member of this group or an Administrator on your workstation to be able to run the WorkSite Administrative Tools. Customize the database captions and dialog boxes using the Dialog Editor.

(57)

Additional Tasks

(58)

(59)

Appendix A

Recommended SQL

Maintenance Tasks and

Scheduled Dumps

Overview

To ensure the health and ability to restore your SQL database, Autonomy highly recommends installing a series of scheduled maintenance tasks and database dumps on your SQL Server. This appendix provides instructions for configuring the following tasks:

Back up of the WorkSite databases (Full)

Back up of the WorkSite database (transaction logs) Integrity check of the database tables

Rebuilding the Index

These tasks can be scheduled using the Microsoft SQL Server Management Studio. The instructions provided are guidelines. You may want to customize these tasks for your specific installation.

NOTE

Autonomy is not liable for any data loss that might result from the use of these

recommendations. Microsoft provides extensive documentation for the use of the tools described here. Several Microsoft Certified training centers are also available that provide specialized training on SQL Server administration. Autonomy recommends that only a certified and trained SQL DBA set up these tasks.

(60)

Appendix A: Recommended SQL Maintenance Tasks and Scheduled Dumps

Recommended Maintenance Plans

Autonomy recommends creating the following plans Every two hours. Back Up Database (Transaction Log) Every night. Update Statistics, Back Up Database (Full)

Once a week. Database Integrity Check, Back Up Database (Full), and Rebuild Index

After the maintenance plans are scheduled, make sure that these plans execute on a regular basis by checking the backup and the log directories. These directories and log files must be checked daily. If the maintenance plans are malfunctioning, call Microsoft SQL Server Technical Support.

Creating a Maintenance Plan for WorkSite

Databases

The maintenance plan for WorkSite databases includes the following sections: Configuring the Check Database Integrity Task

Configuring the Rebuild Index Task

Configuring the Update Statistics Task

Configuring the Back Up Database (Full) Task

Configuring the Back Up Database (Transaction Log) Task Completing the Maintenance Plan

Using the SQL Server Management Studio you can create a maintenance plan for each database. 1. Launch the Microsoft SQL Server Management Studio.

2. In the Object Explorer, expand a server and then expand Management. 3. Right-click Maintenance Plans and select Maintenance Plan Wizard.

(61)

Creating a Maintenance Plan for WorkSite Databases

Figure 32 SQL Server Management Studio

(62)

Figure 33 SQL Server Maintainence Plan wizard

(63)

Figure 34 Select Plan Properties

5. Enter a name for the maintenance plan. 6. Select Separate schedules for each task.

(64)

Figure 35 Select Maintenance Tasks

8. Select the following options: Check Database Integrity, Rebuild Index, Update Statistics, Back Up Database (Full) and Back Up Database (Transaction Log).

NOTE

Statistics are updated as part of the Rebuild Index task. If the Auto-Update Statistics option is disabled in Database Properties, a daily task to Update Statistics is recommended.

NOTE

The type and frequency of database backups will be determined by each customer's disaster recovery plan.

(65)

Figure 36 Select Maintenance Task Order

10. Use the Move Up and Move Down buttons to set the tasks in the following order: Check Database Integrity

Rebuild Index Update Statistics

Back Up Database (Full)

Back Up Database (Transaction Log)

11. Click Next. Continue with “Configuring the Check Database Integrity Task” on page 66.

NOTE

The order of the tasks set here is designed to match the order of the task configuration instructions that follow in this document. The actual order in which the tasks are performed will be defined by their scheduled times.

(66)

Configuring the Check Database Integrity Task

The Define Database Check Integrity Task appears.

Figure 37 Define Database Check Integrity Task

(67)

Figure 38 Database selection panel

13. Select These databases. 14. Select the WorkSite database. 15. Click OK.

(68)

Figure 39 Defining Database Check Integrity task

16. Select Include indexes.

(69)

Figure 40 Job scheduling for Database Integrity check

18. Schedule the frequency of the Check Database Integrity task. This should occur at least once a week during the scheduled maintenance period. The task should run prior to database backup.

(70)

Figure 41 Configured database integrity task

This completes the configuration of the Check Database Integrity task. 20. Click Next. Continue with “Configuring the Rebuild Index Task” on page 70.

Configuring the Rebuild Index Task

(71)

Figure 42 Configuring the rebuild index task

21. Click the Databases drop-down menu and select all WorkSite databases as shown in step 12

to step 14.

22. In the Object dop-down list select Table. 23. In the Selection drop-down list select All.

24. In the Free Space Options section, select Change free space per page percentage to and set the value to 10%.

25. In the Advanced Options section, clear the check boxes for Sort results in tempdb and

(72)

NOTE

Keep index online while reindexing is not recommended because some WorkSite tables use

LOB data types. Indexes with this data type cannot be rebuilt while online.

26. In the Schedule section, click Change. The Job Schedule Properties dialog box appears.

Figure 43 Job scheduling for rebuilding the index task

27. Schedule the frequency of the Rebuild Index task. This should occur at least once a week during the scheduled maintenance period. The task should run after database backup. 28. Click OK. The updated Define Rebuild Index task window appears.

(73)

Figure 44 Updated rebuild index task window

This completes the configuration of the Rebuild Index task.

29. Click Next. Continue with “Configuring the Update Statistics Task” on page 73.

Configuring the Update Statistics Task

The configuration window is displayed only if the Update Statistics task was selected from the maintenance task list. See Figure 36 on page 65.

(74)

Statistics are updated as part of the Rebuild Index task. If the Auto-Update Statistics option is disabled in Database Properties, a daily task to Update Statistics is recommended.

The Define Update Statistics Task window appears.

Figure 45 Defining the update statistics task

30. Click the Databases drop-down menu and select the WorkSite databases as as shown in

(75)

34. In the Scan type section, select Full scan.

35. In the Schedule section, click Change. The Job schedule Properties dialog box appears.

Figure 46 Job schedule for updating statistics

36. Schedule the frequency of the Update Statistics task. This should occur at least once a day during the scheduled maintenance period. The task should run prior to database backup. 37. Click OK. The updated Define Update Statistics task window appears.