Documente Academic
Documente Profesional
Documente Cultură
eDOCS DM 5.3
Open Text Document Management, eDOCS Edition
eDOCS DM Installation Guide
Rev.: November 2010
This documentation has been created for software version 5.3.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at: https://knowledge.opentext.com.
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
E-mail: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit: http://www.opentext.com
Copyright by Open Text Corporation, Open Text Inc.
Open Text Corporation is the owner of the trademarks Open Text, The Content Experts, Open Text ECM Suite, Open Text
eDOCS, eDOCS, Open Text FirstClass, FirstClass, Open Text Exceed, Open Text HostExplorer, Open Text Exceed
OnDemand, Open Text Exceed 3D, Open Text Exceed Freedom, Open Text Exceed PowerSuite, Open Text Exceed XDK,
Open Text NFS Solo, Open Text NFS Client, Open Text NFS Server, Open Text NFS Gateway, Open Text Everywhere, Open
Text Real Time, Open Text Eloquent Media Server, Open Text Integrated Document Management, Open Text IDM, Open
Text DocuLink, Livelink, Livelink ECM, Artesia, RedDot, RightFax, RKYV, DOMEA, Alchemy, Vignette, Vizible, Nstein,
LegalKEY, Picdar, Hummingbird, IXOS, Alis Gist-in-Time, Eurocortex, Gauss, Captaris, Spicer, Genio, Vista Plus,
Burntsand, New Generation Consulting, Momentum Systems, DOKuStar, and RecoStar among others. This list is not
exhaustive.
All other products or company names are used for identification purposes only, and are trademarks of their respective
owners. All rights reserved.
Contents
Setting Up eDOCS DM 1
What Youll Need to Get Started 2
Notes on the First-Time Installation Process 2
Install and Prepare SQL Servers 2
Install SQL Client on DM Servers 3
Create DM Server Service Account 3
Install DM Server and Generate Library 3
Install DM Web Server 4
Populate Library with Your Organizations Data 4
Install Security Service on Document Server and Import Existing
Documents 5
Set Properties in DM Server Manager 6
Create SearchServer Indexes 6
Using Transforms to Include DM-Related Items 6
Specifying Features on a Command Line for Scripted Installs 7
MSI Install Options 7
DM Extensions Examples 10
eDOCS DM MSI Silent Install Samples 11
Services 11
Configuring Windows Server 2008 Firewall to Allow NetTCP Connection
11
Installing eDOCS DM Components 13
Using the eDOCS Suite Installer 14
Whats Installed with DM Server 15
Installation Prerequisites 16
Installation Steps for DM Server 17
Configuring the DM Server 19
The DM Server Administration Tools 22
iii
Installing DM Web Server 23
Installation Prerequisites 23
Installation Steps for DM Web Server 24
27
Generating a Library 29
Before Generating a Library 30
The Internal User 30
Consistency of Library Names 31
Maximum Number of Documents in a Library 31
Updating a Library 31
Steps in Library Generation 32
Using Mixed and Windows Authentication for SQL Server
Authentication 65
Changing Database Access from Trusted Connection 65
Creating an Index 69
Running the Wizard 70
Installing DM WorkFlow 81
Before You Begin 82
Installation Prerequisites 82
Configuration Choices 83
DM WorkFlow Server Components Overview 84
Installing DM WorkFlow Server Components 86
Synchronizing Users 88
Post-installation Information 90
DM WorkFlow Administration 90
Setting Up a DSSS Document Server 91
NOS-Level Security for Document Files 92
Implementing DSSS 92
Installing the DSSS Software 93
Configuring DSSS to Run Under Domain Account 94
Creating Windows Groups and Adding Them to the DM Library 94
Adding a Global Group to a DM Library 96
Adding a Local Group to a DM Library 97
iv
Multiple Domain Aliases 97
Creating a Windows Share and Granting Users Access 99
Configuring the Document Server 104
Starting and Stopping DSSS 105
On Windows Server 105
Troubleshooting DSSS 106
Setting Up a DSSA Document Server 107
About DSSA 108
Understanding How DSSA Works 108
DSSA System Requirements 109
Prerequisites for Installing DSSA 109
Installing the DSSA Service 110
Creating a Windows Share and Granting Users Access 112
Configuring a DSSA Document Server 115
Viewing the Audit Trail 116
Installing RM 119
Related Manuals 120
Installing RM 120
Installing RM on DM Server 120
Installing RM on DM Web Server 121
Prerequisites for Installing RM Administration Tool 122
Installing RM Administration Tool 122
RM.INI and PCDOCS.INI File Locations 124
Additional RM Installation Information 124
Assigning RM Forms 124
Enable Logging 125
Configure a Client for RM Custom Reports 125
Uninstalling RM Administration Tool 126
Installing DM Extensions 127
Before You Begin 128
Installation Prerequisites 128
Install DM Extensions 128
Removing DM Extensions 131
v
Installing the eDOCS DM API 133
Installing eDOCS DM API 134
Removing DM API 134
Configuring eDOCS Imaging 135
Installing the IIDS 136
Configure Internet Imaging Document Server 136
Important Workstation Configuration 138
Set Internet Explorer Security Options 139
Enable Plugin in DM Webtop 139
Pointing a Component to a Different DM Server 141
Running the DM Connection Wizard 142
Setting Up the DM Server
Service Account 145
About the DM Server Service Account 146
Setting Up Accounts on Windows Servers 146
Creating the Account 147
Adding the Account to the Local Administrators Group 147
Applying Rights to the Account 147
Special Considerations for Microsoft SQL Server Libraries 149
Installation Impact on Regular Operations 150
Dedicated SQL Server Machine 150
Windows Service Accounts 150
Support for Microsoft SQL Server 2005 151
Database and Document Servers 151
Document Servers 151
Database Servers 151
Configuring SQL Servers and Databases 152
LAN Environments 152
WAN Environments 153
Disk Space Requirements 153
SQL Server and System Files 153
DM Database 154
Memory Requirements 158
vi
User Connections 159
Worksheets 162
Server Configuration Worksheet 162
SQL Server Installation Worksheet 163
Database Configuration Worksheet 164
Installation Worksheet 165
Special Considerations for Oracle Libraries 167
DM Requirement for Oracle Databases 168
Multiple Libraries on a Single Oracle Instance 168
Owner Accounts 168
Tablespace Names 168
Rollback Segments 169
Mixed-Case Data and Case-Insensitive Searches 169
Selecting Mixed-Case Storage During Library Generation 170
INIT.ORA Modifications for Mixed-Case Data 170
Removing Indexes to Improve Performance 170
DM WorkFlow Oracle Tablespaces 173
The PCDOCS.INI File 175
Location 176
Settings 176
Troubleshooting 179
Accessing Our Knowledge Base 180
Check the Setup of the DM Server Service Account 180
Problems Locating DM Server 182
NetWare Connectivity 183
Miscellaneous Issues 183
Problems with the Microsoft SQL Client Software 185
Microsoft SQL Server Errors 185
Error #1105 185
Error #9002 186
Error #10004 187
Decreased Performance or High Server Utilization 187
vii
Problems with the Oracle Client Software 188
Index
viii
Chapter
1
Setting Up eDOCS DM
In This Chapter
1
What Youll Need to Get Started
To install and configure eDOCS DM, you will need the following:
Software
SQL Database server installation software and
documentation
Internet Information Services (IIS) Web server software
Web browser software
eDOCS DM installation files, serial numbers and
documentation
Computers The number of computers required depends on
your repository size.
SQL Database Server
DM Server
DM Web Server
DM Indexer
Network Resources
Network share(s) to store documents
NOTE: See the Release Notes for specific hardware and software
requirements..
2 CHAPTER 1
New or recently edited documents that need full-text
indexing.
Archival data.
Other information pertaining to management of
documents and the DM system itself.
For specific details on supported SQL databases, see the Release Notes.
NOTE: For instructions on setting up a SQL database, see the appendix for
your SQL implementation and your database vendors documentation.
Install SQL Client The SQL client software, which allows a user account to connect to the
on DM Servers database, must be installed on all DM Servers.
For instructions on installing the SQL client, see your database vendors
documentation.
Create DM Server The DM Server software must be run under an administrator account,
Service Account such as DMADMIN. The account must exist before you install the DM
Server software. See Setting Up the DM Server Service Account for
information on the rights and abilities required for the DM Server
service account.
Install DM Server The DM Server software includes DM Server, the Server Admin Tools,
and Generate SearchServer, the Hummingbird Core Services (HCS) Authentication
Library Client, and the user-interface forms that display and accept data from
DM client users.
Installation of the DM Server software also installs the user-interface
forms. The default location for the forms is \Program Files\Open
Text\DM Server\DOCSObjects. If you move the forms, remember that
they must be accessible to DM Server and all DM client users. Be sure
to specify the new location on the Preferences tab of the DM Server
Manager. See the DM Administration Guide for more information.
After the installation, the DM Server Configuration Wizard will run to
help you set up the DM Server. The wizard will also run Library
Generator to create the DM tables in the SQL database. The library
generation process populates the SQL database with standard
information for all DM libraries. It also gives you the option of
synchronizing network users with DM users, copying network users
and groups into the library so you need not add each one manually.
Install DM Web The DM Web Server software should be installed on a server machine
Server that is accessible to the DM Server(s). DM Web Server runs the DM
Webtop and is also used for administration of the library,
customization of the DM Webtop.
Prior to installing DM Web Server, Microsoft Internet Information
Services (IIS) must be installed on the machine. Consult the Release
Notes for the supported versions of IIS.
End users will need to know the DM Web Servers URL to access DM
from their browsers.
Populate Library Once a library is generated, these additional steps should be performed
with Your to get the library ready for users:
Organizations Select feature, utility, and version-control options for all
Data users. See the DM Administration Guide for instructions.
Add Document Types. See the DM Administration Guide for
instructions.
To import Document Types from an ASCII text file, use the
Database Import tool. To use this tool, on the DM Server,
click Start>Programs>Open Text>DM Server>Server Admin
Tools>Database Import. See the tools Help system for
instructions.
Add users and groups. There are several methods for adding
users:
Synchronize users and groups in the library with
network users and groups. See page 60for instructions.
4 CHAPTER 1
Add users manually with Library Maintenance>People.
See the DM Administration Guide for instructions.
Import users from an ASCII text file with the Database
Import tool. To use this tool, click Start>Programs>Open
Text>DM Server>Server Admin Tools>Database Import. See
the tools Help system for instructions.
Create groups of users that require the same rights and
features. All users are members of the group DOCS_USERS.
There are two methods for adding groups to the library:
Synchronize with network groups. See page 60 for
instructions.
Add groups manually with Library
Maintenance>Groups. See the DM Administration
Guide for instructions.
Set up remote libraries. See the DM Administration Guide
for instructions.
Customize forms and database tables. Refer to the DM
Designer Guide for more information.
Install Security A document server is an area designated for storage of documents. All
Service on electronic documents in your library will be stored on one or more
Document Server document servers. The DM Administration Guide explains how to set
up document servers.
and Import
Existing If your document servers are Window Server machines, and depending
Documents on the security needs of your organization, you may want to install one
of the DM security services DSSS or DSSAon the document server.
See the chapter titled Document Access and Security in the DM
Administration Guide for a explanation of what these security services
can offer. For installation instructions, see Setting Up a DSSS
Document Server (for DSSS) and Setting Up a DSSA Document Server
(for DSSA).
After installing the security service (if applicable), you should then
identify the document server to the library via Library Maintenance,
either from DM Server or the DM Admin tab of DM Webtop. Once a
document server has been identified, you can import existing
electronic documents into it using the Document Import tool. During
the import process, DM creates a Document Profile in the library for
each imported document. To use the Document Import tool, on the
Create You have the option of giving users the ability to do full-text searches of
SearchServer documents and profile data in the DM repository. This means users can
search for documents by specifying a word or phrase contained in the
Indexes contents of documents. To provide this capability, you must set up the
indexing of documents by DM Indexer using SearchServer.
See Creating an Index for instructions on creating an index.
6 CHAPTER 1
Specifying Features on a Command Line for Scripted
Installs
The MSI installer can be launched from a command line or batch file
with feature selection done through properties passed to
MSIEXEC.EXE. The Features are DMServerFeature, RMServerFeature
and ContentCacheFeature. The serialnumbers for each feature can be
specified using OT_SERIALNUMBER_##="<password>" where ## is
replaced by 17 for the DM Server, 37 for the RM Server and 42 for
Content Caching. The passwords are specified using OT_PASSWORD_##
with the same number substitution.
Below is a sample install script to install everything except the RM
Server; it includes the serial numbers and passwords for the DM Server
and Content Caching passed in on the command line.
ADDLOCAL="ALL" starts with all features selected.
Msiexec.exe /q /i DMServer.msi ADDLOCAL="ALL"
REMOVE="RMServerFeature" OT_SERIALNUMBER_17="17-
XXXX-XXX-XXXXXXXX" OT_PASSWORD_17="xxxxxxxx"
OT_SERIALNUMBER_42="42-XXXX-XXX-XXXXXXXX"
OT_PASSWORD_42="xxxxxxxx"
MSI Install Options The following are MSI install options; consult the MSI documentation
for more information.
Install Options
</package | /i> <Product.msi> Installs or configures a
product
Display Options
/quiet Quiet mode, no user interaction
n No UI
b Basic UI
r Reduced UI
f Full UI (default)
Restart Options
/norestart Do not restart after the installation is complete
Logging Options
When the *.msi for the install is invoked using MSIEXEC.EXE, you can
use the -l logging option to create a log of the install.
If you use the Open Text eDOCS Suite Installer, you can configure
logging during the installation.
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i Status messages
w Nonfatal warnings
8 CHAPTER 1
a Start up of actions
r Action-specific records
u User requests
c Initial UI parameters
o Out-of-disk-space messages
p Terminal properties
v Verbose output
Update Options
/update <Update1.msp>[;Update2.msp] Applies update(s)
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p only if file is missing
DM Extensions The DM Extensions MSI takes the licensed product's serial number/
Examples password on the command line, to support the silent install.
OT_SERIALNUMBER_28
OT_PASSWORD_28
OT_SERIALNUMBER_32
OT_PASSWORD_32
Non-Silent Install
msiexec /l*v "%TEMP%\dmext.log" /i "C:\ eDOCS DM 5.3
Extensions (x86).msi" (non-silent install)
10 CHAPTER 1
eDOCS DM MSI To obtain additional information on the scripting and configuration
Silent Install options and samples, consult the eDOCS DM MSI Silent Install Samples
Samples Application Note in the Knowledge Center at the following location:
https://knowledge.opentext.com/knowledge/cs.dll/Open/18813090
Services
The following shows the eDOCS DM services that are installed:
SERVICES 11
To configure Windows Server 2008 firewall to allow NetTCP
connection:
1. On the Windows 2008 Server, click Start>Administrative
Tools>Windows Firewall with Advanced Security.
2. In the left pane, right click Inbound Rules and select New Rule.
3. The first dialog asks what type of rule you want to create.
Select Port and click Next.
4. By default, the DM client set to NetTCP will use port 808, so
type 808 and click Next.
5. Select the Allow the connection option.
6. Select Domain and click Next.
7. Give the rule a name and click Finish.
Your DM client machines will now be able to connect to a Windows
2008 Server with the firewall still active.
12 CHAPTER 1
Chapter
2
Installing eDOCS DM
Components
In This Chapter
13
Using the eDOCS Suite Installer
The eDOCS Suite Installer (eDOCSSuiteInstall.exe) allows you to
install all eDOCS DM components from an installation wrapper.
Although you can install DM components from the individual MSIs,
this installer sorts the components in the order in which they should be
installed. You can easily install these components from the eDOCS
Suite installer, which executes each of the individual MSIs.
To use the eDOCS Suite Installer:
1. Locate and double-click the eDOCSSuiteInstall.exe file.
2. The eDOCS Suite Install dialog box opens.
14 CHAPTER 2
eDOCS DM Extensions
eDOCS DM Documentation
You must install DM Server first. Select eDOCS DM Server and
then click Next.
3. The Options for eDOCS DM 5.3 <component name>
dialog box appears. The Commandline field shows the
parameters set for installing the product, such as the
location of the products MSI.
If you want an installation log file created, select the Create a
log file check box. Notice that the location and file name of
the log file appear in the Commandline field. The default log
file location is C:\DMLogs\.
The log file name has the following naming convention:
<Component name>_<date>-<time>.log. For example,
DMServer_1101-1159.log, which indicates the DM Server
installation started on November 1 at 11:59 a.m. The 24-
hour time is used.
4. The Option parameter(s) field is for advanced users only. You
can specify additional parameters to be added to the
Commandline field.
5. Click Install.
6. The Welcome to the Open Text eDOCS DM 5.3 <component
name> Setup Wizard appears.
See Installation Steps for DM Server to complete the
installation.
7. When the component installation is finished, go back to the
eDOCS Suite Installer and repeat the above steps for each
component you want to install.
When you select the eDOCS DM Documentation component, all of the
documentation PDFs are copied to the \Program Files\Open
Text\Documentation directory.
Whats Installed
with DM Server DM Server \Program Files\Open Text\DM Server
16 CHAPTER 2
The Event Log service process must be running for DM Server to start.
We strongly recommend that you set your Event Logs to overwrite as
needed. This is both for DCOM messages when the DM Server is
stopped and for SearchServer indexing messages.
Exit any programs that are currently running on the server machine.
Installation Steps 1. On the server where you are installing DM Server, log on
for DM Server under a local Windows Administrator account with the
advanced right Act as part of the operating system. It is not
required that the account be the DM Server Service account.
You can click the Disk Usage button to view each available
drive with their Disk Size and Available space.
Click Next.
6. The Choose Products for Licensing dialog box appears.
Enter the Serial Number and Password and then click Next.
Continue this step for each product you selected to install.
7. The Destination Folder dialog box appears. The default
installation is C:\Program Files\Open Text\DM Server.
Click the Change button to select a different directory, or
click Next.
8. The Ready to install dialog box appears. Click Install to begin
the installation.
9. The Installing Open Text eDOCS DM Server 5.3 dialog box
appears with a Status bar indicating the progress.
10. When the installation is finished, the Completed the Open
Text eDOCS DM Server 5.3 Setup Wizard dialog box
appears. Click Finish.
18 CHAPTER 2
11. After you click Finish, the DM Server Configuration Wizard
starts. See the next section, Configuring the DM Server, for
instructions.
Configuring the The DM Server Configuration Wizard assists you in setting up the DM
DM Server Server.
Most of the options you set here can be changed later in the DM Server
Manager. The only exception is the specification of the DM Server
service account. To specify a different account, you must run the
Configuration Wizard again.
20 CHAPTER 2
Otherwise, click Next, and continue with step 19.
4. If you clicked Create Library, the Library Generator dialog box
appears, which states: This program will initialize a
database and also update a database created for earlier
versions. Is this what you want to do?
Click Yes.
5. The Industry-specific Customization dialog box appears.
Select one of the following industry types to install sample
customizations for your profession. If you do not want any
customization, select Default:
Default
Financial
Government
Legal
Click OK.
6. The Library Generation dialog box appears, where you
indicate the library name and brand of SQL software. If a
library already exists, select the Library Name from the drop-
down menu; otherwise, type the library name. In the SQL
Vendor section select either MS SQL Server or Oracle, and then
click OK.
7. The SQL Server Selection dialog box appears. Select the SQL
Server Name from the drop-down list (or type it) and click
OK.
8. The Database Selection dialog box appears. You can select
an Existing Database or click Create New. If you select an
existing database, click OK.
9. The Database Owner Name and Password dialog box
appears. Enter the DOCSADM Password. Click OK.
10. The Select Primary Document Server dialog box appears. In
the Physical Location field, type the drive where your
document files will be stored.
Click the Operating System drop-down menu and select the
type.
Click OK.
11. The Updating Database Structure dialog box appears, which
shows the database tables being built.
The DM Server The DM Server Administration Tools are installed automatically when
Administration you install DM Server. Access these tools through Start>Programs>Open
Tools Text>DM Server>Server Admin Tools. Consult the tools Help systems for
instructions.
22 CHAPTER 2
Installing DM Web Server
The name of the computer where you are installing DM Web Server should not
contain non-DNS characters such as underscores.
24 CHAPTER 2
4. The Custom Setup dialog box appears with the following
installation options:
26 CHAPTER 2
8. The Destination Folder dialog box appears. The default
installation location is C:\Program Files\Open Text\DM
Web Server. Click the Change button to select a different
location; otherwise, click Next.
9. The Ready to install dialog box appears. Click Install.
10. When the Completed the Open Text eDOCS DM Web
Server Setup Wizard dialog box appears, click Finish.
.
27
Chapter
3
Generating a Library
In This Chapter
29
Before Generating a Library
Library generation adds the DM tables to a database created on your
SQL server. Prior to running Library Generator, you must:
Install the SQL server engine and create a SQL database.
Your SQL vendors documentation provides instructions on
installing the SQL engine and creating a database.
See one of the following appendices in this manual for
specific considerations for your SQL type:
Special Considerations for Microsoft SQL Server
Libraries
30 CHAPTER 3
document previews. You may use the INTERNAL account created
during library generation or you may create another account for this
purpose. See the chapter on indexing in the DM Administration Guide
for more information on the internal user account.
Updating a Library
32 CHAPTER 3
Sites upgrading from earlier releases of DM need not update a library
during installation, but all existing libraries must be updated with the
current version of Library Generator before they can be used with DM.
To create or update libraries after installing DM Server, run Library
Generator from the Start menu (Programs>Open Text>DM Server>Server
Admin Tools>Library Generator). The behavior of Library Generator is the
same, whether you start it this way or run it during the DM Server
installation.
34 CHAPTER 3
The following industry customizations are available:
Note: If you want to create your own custom tables and forms or modify the
industry-specific tables and forms provided, use DM Designer. Refer to the
manuals DM Designer Guide and DM/RM Data Dictionary for more information.
36 CHAPTER 3
5. On the Login dialog box, enter the SQL system
administrator account name and password. This account
will be used to create a SQL Server user account that will be
the library owner.
38 CHAPTER 3
In the Imported Documents field, enter the number of
documents to be imported into the database. This allows
Library Generator to calculate the display, in the File Size
field, the recommended size for the database file. You can
modify this value if you like. The default value for the File
Size field is 15 Mb. Note that the log file size is computed to
be one third the size of the database file. Click OK to
continue.
The Database Selection dialog box returns with the new
database name in the Existing Databases list. Make sure the
name is highlighted and then click OK.
40 CHAPTER 3
11. Oracle libraries only. On the Login dialog box, enter the SQL
system administrator account name and password. Click OK.
42 CHAPTER 3
Oracle libraries only. If you are generating a new Oracle
library, an Information dialog box is displayed, informing
you that, unless you are told otherwise, tablespaces are
created in the Oracle default directory and tablespaces
should be on different disk drives, if possible. If you will
have multiple Oracle instances, you will need to specify the
complete path for the tablespace names in order to avoid
naming conflicts. Click OK.
44 CHAPTER 3
Enter the approximate initial number of documents to
be imported.
Enter an approximate number of documents to be added
in the next year.
Enter an approximate number of people who will be
accessing the library database.
If you selected an industry type other than default, enter
the appropriate information as requested.
The numbers need not be precise, but your database will
perform better the more exact your estimations. When you
have made your estimates, the disk space requirements are
displayed at the bottom of the dialog box. Click OK.
Now skip to step 31. Note that steps 16 through 30 apply
only to users selecting the Custom option.
16. Oracle libraries only. If you select Custom, the Oracle Custom
Install dialog box is displayed.
46 CHAPTER 3
library, they increment to DOCSPROF2, DOCSVAL2,
DOCSIND2, DOCSTMP2. In the example below, the
tablespaces are being created for the eighth library on the
instance. Up to 100 libraries can be created using the default
tablespace names.
48 CHAPTER 3
25.2 On the Table Information Maintenance dialog box,
modify the tables storage parameters as necessary.
50 CHAPTER 3
26.1 Highlight the tablespace you want to edit and click
Edit.
52 CHAPTER 3
28. Oracle libraries only. When you have finished editing the
table and tablespace information on the Oracle Tablespace
Selection dialog box, click OK to bring up the Oracle
Temporary Tablespace Creation dialog box. DM requires
you to define a temporary tablespace.
File Name: The name of the tablespaces data file. The default
is DOCSTEMP.DBF. If no path is specified for the file, it will
be created in the Oracle default directory, so you should
enter a path here. The full path and file name must be
unique on the server.
54 CHAPTER 3
Note: If the block size for your Oracle instance is larger than
4 KB, enter zero for the number of rollback segments.You
must create any additional rollback segments manually.
30. Oracle libraries only. On the Create Redo Log Files dialog
box, specify the number of additional redo log files to be
created for your database.
Current number of redo log files: The number of redo log files
currently available for the database.
Maximum number of redo log files allowed: The maximum
number of redo log files allowed by your operating system.
Additional redo log files to be created: The number of
additional redo log files to create for this database.
Directory name: The full path where the redo log files should
be created. You must enter a path here.
56 CHAPTER 3
To implement NOS-level security on a Windows document
server, you must run either the Document Server Security
Service (DSSS) or the Document Server Sentry Agent
(DSSA). Both security services are provided with DM. For
DSSS installation and setup instructions, see Setting Up a
DSSS Document Server. For DSSA installation and setup
instructions, see Setting Up a DSSA Document Server.
33. During this process, you are asked if you want to allow
duplicate document names in the library.
35. Select the Use Trusted Connection check box to allow your
users to authenticate using either the common logon or
through Windows Authentication.
Note: If you click Cancel at the Common SQL Login dialog box, the common
login scheme is used with DOCSADM as the login account.
58 CHAPTER 3
36. On the Application Integration dialog box, the applications
you select determine what applications are shown in end-
users displays, provided that the selected applications have
been integrated with DM.
38. The User Synchronization dialog lets you add users to the
library. You can add users now, or laterusing the Library
Maintenance tool on the Start menu or via the User tab in
DM Admin on the DM Webtop. We recommend you add
users later and that you click Close now and skip to step 40
on page 64.
60 CHAPTER 3
If you prefer to add users now:
38.1 To import users contained in any of the network
objects displayed, highlight the item in the Network
Resources list and click Import Users.
Network Resources: The Network Resources list displays
all available networks. Double-click a network to
display domains, servers, countries, or organizations
depending on the network selected. In hierarchical
networks, such as NetWare, you can display the entire
network tree. To display the users in a particular object,
double-click the object to expand the list.
Library Users: The Library Users list displays the current
users of the library and their network aliases. If this is a
new library, the only valid library user is the user
executing Library Generator. Double-click a user to
display his or her associated network aliases.
62 CHAPTER 3
38.5 To remove a network alias, highlight the alias in the
Library Users list and click Remove Alias. The selected
network ID is no longer associated with a user in the
library.
38.6 When you have completed user synchronizations, click
Close.
39. Oracle libraries only. We strongly recommend you click Print
on the Important Notice dialog box to print the list of
rollback segments created for Oracle. After library
generation is complete, you will need to add these segments
to INIT.ORA so that the segments will come back online
should the Oracle instance ever be restarted. When the print
job is finished, click OK.
Note: This dialog box does not appear for Oracle 9i databases whose
undo_management setting in INIT.ORA is set to AUTO.
From this point, you need to take the following steps to prepare the
library for production use:
Changing Database When you create a database, you can select the Trusted Connection check
Access from Trusted box when you generate the DM library in Library Generator.
Connection However, there is no configuration user interface to revert to the other
database login method. When you create a library you must supply
66 CHAPTER 3
TrustedConnection=yes
[Library Trusted]
Vendor=3
Database=Trusted
Owner=
Location=localhost
;TrustedConnection=yes
UserName=DOCSUSER
Use [LibraryDBName]
GO
4
Creating an Index
In This Chapter
69
DM Indexer in the DM Administration Guide for more information on
full-text indexing.
70 CHAPTER 4
Started. The index is available for searching and for
indexing of new and revised documents.
Stopped. The index is available for searching but is not
available for indexing of new and revised documents.
Paused. The index is available for searching, but it is not
available for indexing of new and revised documents
because the DM Indexer is paused for system maintenance.
When the DM Indexer resumes operation, the index will be
available for indexing.
4. To create a new index, select the check box Create new index
and click Next. Then follow the instructions on the Create
Indexes page. If you don't want to create an index, clear the
check box and click Next.
If you do not want to create a new index now, clear the
check box and click Next. Then skip to step 7.
5. The left pane of the Create Indexes dialog box shows the
libraries you have selected to be available to DM users. Click
to insert a check mark next to the library you want to create
an index for and click Add.
Note: The Remove button lets you delete the database entry
for indexes you have created but not yet initialized. It cannot
be used to delete indexes that contain data.
72 CHAPTER 4
Index Name: If you want to change the default index
name, modify the name in this field.
Data Source Name: By default, DM Server assigns an
index a data source name in the format <library
name>_<number>.
PathDefault: Select Default to store the index in the
default location, a location which was specified when
you installed the DM Server software on the Indexer
server. (By default, this location is C:\Documents and
Settings\All Users\Application Data\Open Text\DM
Indexes. .) To store the index in a different location,
clear the Default check box and enter the Path.
RemoteShared: The option you select here depends
on whether you are running Server Manager from the
Indexer server or from a DM Server that handles
requests from DM Webtop users.
Select Shared if the Indexer server is the local machine
and users will be accessing the index via other DM
Servers or KM. Then select the appropriate Network
Protocol and Port so that users accessing the local
server can locate the index. The port cannot be used by
other indexes on the server or by other software using
the network. For Named Pipes, the port is the name of
the pipe (for example, ftnet). For TCP/IP, the port is
the TCP port number (for example, 3048). The TCP\IP
port number cannot be in use on the local system. (To
determine the port numbers in use, run NETSTAT at a
command-line prompt.) Normally, anything higher
than 5000 is a usable port number.
Note: Once a port number has been assigned to an
index, it cannot be used again until you run
\SSK\BIN\FTSVCADM.EXE to remove unused port
numbers. (Do not remove port number 16547; it is
used by DM Server.) After removing the ports, restart
the DM Server service. At this point, you can then add
a new index with the previously used port number.
The Remote option is automatically selected if you
create a shared index on one server and are viewing the
properties of that index on another server.
74 CHAPTER 4
Advanced: This button invokes the Advanced Index
Properties dialog box. When you select a language,
most of the advanced properties are modified to the
defaults for the language. A description of the
advanced index properties can be found in the chapter
on indexing in the DM Administration Guide.
76 CHAPTER 4
6.3 Log File tab:
78 CHAPTER 4
Use All Indexes in Sequence. Using all the indexes in a
round-robin fashion to improve search performance. In this
mode, the first search request goes to the first index in the
list, the second request to the second index, and so on, until
the end of the index list is reached, and the first server
accepts another request.
Use Next Index in List Only When Current Index Fails.
Using a single index as the primary index and the others as
backups in case the first index is not available. In this mode,
when the primary index fails, search requests go to the next
index in the list until the primary index returns to service.
To see all indexes for a libraryincluding those that are not
selected for user searchinghighlight the library name and
click Add. To make another index available for searching,
highlight the index name and click OK. The index is added
to the Indexes Available to DM Webtop Users list.
To change the order of an index in the list, highlight the
index and click the Up or Down key. The Remove key
deletes an index from the list.
11. Click Finish to exit the wizard.
5
Installing DM WorkFlow
In This Chapter
81
Before You Begin
82 CHAPTER 5
Access to the network and to all document servers, libraries,
and SQL databases. The DM WorkFlow service account is
not required to be a domain account, but we strongly
recommend that you make it a domain account because it
must typically access data on other network resources.
"Act as a part of the operating system" rights.
"Log on as a service" rights.
"Log on as a batch job" rights.
Membership in the local administrator group on the local
machine. The account need not be a member of the Domain
Admins group.
Oracle Users
During the first time install of DM WorkFlow Server Components, the
DM WorkFlow Database Generator by default suggests using Oracle
SYSTEM tablespace for USER tables and TEMP for Temporary ones.
See DM WorkFlow Oracle Tablespaces on page 173 for more
information.
Two-machine configuration:
Machine 1: DM WorkFlow Server Components with DM API and
a supported SQL client.
Machine 2: DM WorkFlow with DM API, DM, and a supported
Web server.
Clients: A supported Web browser or DM WorkFlow Extension.
If you install DM WorkFlow Server Components and DM
WorkFlow on two different computers, you must replace the IIS
Anonymous User account with the special domain account or add
the first as a local account on the computer where WorkFlow
You should set a Routing Agent Account to allow the WorkFlow Engine
to run on behalf of this account without logging on.
Note: If you want to enable mail notification you must have a mail client with a
valid user profile installed on the machine with the WorkFlow Engine.
The account you specify must have rights (to at least send mail) on the
mail profile you use for mail notification.
84 CHAPTER 5
To allow users from several DM libraries to use one DM
WorkFlow library, define one of the libraries as a primary
and the others as remote libraries. During the user
synchronization of the installation process, remember to
select the remote libraries and synchronize those users.
Note: At synchronization between several DM WorkFlow sites, the users at
each site must be synchronized with their own sites library: do not select the
same DM library for two DM WorkFlow sites.
If DM WorkFlow Server Components and the SQL server
are installed on different computers, specify the same
Regional Settings with the Set as System Default Locale
option selected.
The common files will be copied into the following directories:
C:\Program Files\Common Files\PCD Shared\Logger
After installing WorkFlow Agent, you must restart the computer. You
will also be asked to restart the computer if you are installing a
component where the one it is replacing is currently loaded in memory.
86 CHAPTER 5
5. The Destination Folder dialog box appears. The default
installation location is C:\Program Files\Open Text\DM
Workflow Server. Click the Change button to locate a
different location, if needed; otherwise, click Next.
6. The DM Server specification dialog box appears. Type the
machine name of the DM Server to which users will initially
log on and click Next.
7. The Workflow Credentials dialog box appears. Specify the
network logon credentials of the account under which the
DM Workflow service will run. See About the DM
WorkFlow (Routing Agent )Account for more information.
Click Next.
8. The Ready to install dialog box appears. Click Install.
9. After the installation begins, the Select Database Type dialog
box appears. DM Workflow requires a database for the DM
Workflow tables. Click the drop-down menu and select
Microsoft SQL Server or Oracle. Click Next.
10. The Server Name dialog box appears. Type the SQL Server
name and then click Next.
11. The Login information dialog box appears. Enter the login
credentials for the SQL administrator. Click Next.
12. The Select Databases dialog box appears. Select the library
to work with and then click Next.
13. The DM Workflow Administrator Account dialog box
appears. Type the password you want for the WFADM
account and then click Next.
14. The DM Workflow Table Generation dialog box appears
prompting, This will remove any previously generated DM
Workflow tables. Are you sure you want to continue? Click
Yes.
15. When the Creating Tables dialog box shows Completed
successfully, click Finish.
16. The Select Database Type dialog box appears. DM Workflow
requires a database for the DM Workflow tables. Click the
drop-down menu and select Microsoft SQL Server or Oracle.
Click Next.
17. Enter the SQL Server name and click Next.
19. The Existing Databases dialog box appears. Select the library
to work with and click Next.
Synchronizing Users
To synchronize users:
1. Select Start>Programs>Open Text>DM Workflow>DM Workflow
Site and User Synchronization.
88 CHAPTER 5
3. The DM Workflow Site and User Synchronization dialog
box appears with the Connection parameters to Current Site and
DM Library details for Remote Site fields. (This example
illustrates a Microsoft SQL Server database: other
database types will have different fields.)
SYNCHRONIZING USERS 89
7. The program is ready to start user synchronization for the
library. On the Complete Synchronization dialog box, click
Finish.
8. When user synchronization finishes, the Synchronization
dialog box appears. Click OK.
1 (this example illustrates a Microsoft SQL Server database: other
database types will have different fields)
Post-installation Information
DM WorkFlow To perform the additional setup necessary for DM WorkFlow, refer to
Administration the DM WorkFlow Administration Guide. This guide includes
information about setting up mail notification, DM WorkFlow Agent
settings and using other administrative utilities.
90 CHAPTER 5
Chapter
6
Setting Up a DSSS Document
Server
In This Chapter
91
NOS-Level Security for Document Files
NOS-level security means that when a document is secured in DM, the
rights assigned to the document apply regardless of whether the
document is accessed from within DM or outside DM via an operating
system mechanism such as Windows Explorer.
Implementing DSSS
Implementing DSSS on a Windows document server involves the
following steps:
1. Install the DSSS software (page 93) on all servers that will be
used as document servers. If you are using a Microsoft
server cluster, you must install DSSS on each node (member
machine) in the cluster.
2. If you are using a Microsoft server cluster, configure DSSS
on each node to run under a domain account rather than
the local system account. The domain account should be the
same for all nodes.
If you are not using a server cluster, DSSS should run under
the local system account. This is automatically set when you
install DSSS.
92 CHAPTER 6
3. Create global groups in the domain for all groups that you
are using in DM (page 94). At a minimum, you must create
the following groups:
DOCS_USERSAll users who need access to the document
server must be a member of this group.
DOCS_SUPERVISORSThe DM Server service account
must be a member of this group.
If your organization does not support the management of
global groups, you can create DOCS_USERS and
DOCS_SUPERVISORS as Windows local groups. See
Creating Windows Groups and Adding Them to the DM
Library on page 94 for more information.
4. Create a shared directory and apply appropriate access
rights to the share. If you are using a server cluster, the
shared directory should be created on a physical disk drive
shared by the cluster.
5. Configure the document server in Library Maintenance
(page 104).
In addition, the DM Server service account must be a member of the
local administrators group on each document server where DSSS is
installed. See Setting Up the DM Server Service Account for more
information on the DM Server service account.
Configuring DSSS If you are using a Microsoft server cluster, configure DSSS to run under
to Run Under a domain account rather than the local system account.
Domain Account To change the account:
1. Open Services from the Control Panel>Administrative Tools or
Start>Programs>Administrative Tools.
2. Select Open Text Document Server Security Service, right-click
and select Properties.
3. On the Log On tab, select This Account and specify the domain
account logon credentials under which the Security Service
will run.
4. Click OK.
a
Install DSSS on the other nodes in the cluster and configure the service
on each node to run under the same domain account you specified in
step 10.c.
94 CHAPTER 6
created for each DM library group. You can then use Library
Maintenance>Group Maintenance>Group Aliases or DM Admin to associate a
DM library groupsuch as DOCS_USERSwith one or more
Windows groups by adding the groups network alias.
The universal access defined in Library Maintenance for the DM library
group applies to all documents on the server. And, when an author
secures a document using a DM library group ID, the access rights he
or she assigns to the DM group apply at the network-operating-system
level.
The following Windows groups can be added to a DM library group:
Global groups. (A global group contains one or more user
accounts from a single domain.)
Global groups let you alias and maintain multiple users in a
single batch for each domain. Global groups can be used
across multiple document servers.
Local groups. (A local group may contain user accounts and
global groups from one or more domains.)
Local groups can be helpful to the DM administrator in a
multiple-domain network, particularly if the administrator
has no administrator rights beyond his or her own domain
or document server. The administrator can create a local
group that includes users or groups from other domains
and assign them access rights to the Windows document
server. Local groups must be created on each Windows
server employed as a DM document server.
When a new domain is added to the network, its users can
be given access to an existing document server by adding the
users or group to the existing local group and the
corresponding DM library group, thus avoiding the need to
run the security regeneration utility, which is required when
using multiple domain aliases.
A combination of the two. For example, you could include
multiple domain aliases in a single local group, alias some
groups to local groups and some to global groups, or use
multiple domain aliases for a DM library group where one is
a local group and one is a global group.
The members of a Windows groupwhether global or localmust
match the members of its network alias in the DM library. If you use a
Adding a Global When you run Library Generator, the DM groups DOCS_USERS and
Group to a DM DOCS_SUPERVISORS are created in the library database and aliased
Library to the Windows groups in the domain where you are running Library
Generator. If you want to access documents in other domains, you will
need to add the network aliases for those domains.
You can do this in DM Admin tab in DM Webtop or Library Maintenance.
DM Admin Instructions
1. In DM Webtop, click the DM Admin tab.
2. Click Users and Groups.
3. Click Groups.
4. Click the group you want to add the alias to.
5. Click Aliases.
6. Double-click the ADS, LDAP, Microsoft, or NetWare tree to
expand.
7. Highlight the Windows group(s) you want to add and click
the >> button. The alias appears under the Groups pane.
96 CHAPTER 6
Adding a Local Once you have created the local group on the network, take the
Group to a DM following steps to add the groups network alias to the DM library:
Library 1. In Library Maintenance, click the Groups icon.
2. Double-click the group name you want to add the alias to.
3. The Group Maintenance dialog box appears; click the
General tab.
4. Click Aliases.
2
5. In the Network Resources pane, double-click the Microsoft
icon to expand. Highlight << LOCAL GROUP >> and click Add
Alias.
6. On the Enter Local Group Alias dialog box, type the
Windows name of the local group and click OK.
Multiple Domain DM supports multiple Windows domain aliases for groups. This
Aliases allows you to associate a single DM library group with multiple
Windows groups in the library.
All existing DM library groups need to have an alias for each domain in
your environment.
The additional group aliases can be added through Group
Synchronization or Group Aliases in Library Maintenance.
98 CHAPTER 6
At the NOS level, the new aliased DM groups need to be
applied to the directory permissions in the same fashion as
the existing groups. Each new group should be added at the
last static directory in the document path template with
Special Access Permissions.
The network group DOCS_USERS and the account under which the
DSSS runs should have full-control access to the new share. If your
environment consists of DM users only, the group EVERYONE can be
added with full-control access to the share instead of DOCS_USERS.
100 CHAPTER 6
5. Click Permissions to bring up the Share Permissions dialog
box.
102 CHAPTER 6
7. In the Permissions dialog box, highlight the SYSTEM account
and select Full Control.
One document server was added during your initial library generation.
To configure additional document servers, you must have supervisory
rights with access to Library Maintenance.
To configure a document server:
17. In Library Maintenance, click Document Servers. Click the
New icon.
18. In the Document Servers dialog box, complete the following
fields:
Physical Location:\\<2000 server name>\<share name>
104 CHAPTER 6
If you are using a Microsoft server cluster, the 2000 server
name should be the name of the clusters virtual server.
Operating System:Server with NTFS
Media Type:Online
The other fields on the dialog box are optional.
Once these steps are successfully completed, users can begin storing
documents on the new document server.
106 CHAPTER 6
Chapter
7
Setting Up a DSSA Document
Server
In This Chapter
This chapter explains how to set up the Document Server Sentry Agent
(DSSA) to provide document security on Windows document servers.
107
About DSSA
The Document Server Sentry Agent (DSSA) gives an extra measure of
security for DM documents stored on Windows document servers, and
Microsoft server clusters running those operating systems. This extra
protection is not apparent to users and requires no additional effort on
their part. On a DSSA document server, the usual security protocol
applies: only users with rights to a document can access that document
in DM.
The security provided by DSSA comes into play beyond the reach of
DM security. On a non-DSSA server, any user who has network rights
to a document can access that document outside DMfrom Windows
Explorer, for exampleeven if he or she has no rights to the document
in the DM library. If the document is on a DSSA server, however, the
sole access to that document is through the DM library, where the
access rights set up by the author apply.
108 CHAPTER 7
What happens when the user closes the document or the users
connection is terminated? DSSA removes the users access rights to the
document. It also appends a record to the documents audit trail.
However, if the user saves the document as a new version, he or she will
still have access to the original document. Once the new document is
closed, the users access rights to the original document and the new
version are removed.
110 CHAPTER 7
3. The Welcome to the Open Text Document Server Sentry
Agent Setup Wizard appears. Click Next.
4. The End-User License Agreement dialog box appears. Select
the I agree to the terms in the License Agreement check box
and then click Next.
5. The Choose Products for Licensing dialog box appears.
Type the Serial Number and Password and then click Next.
6. The Document Server sentry Agent Service Account dialog
box appears.
The Domain Account Name field refers to the DSSA admin
account under which the DSSA service logs on to the
Windows server. This account will own all documents and
their corresponding access control lists and audit trails
stored on the DSSA document server.
The account must be a domain account that is a member of
the domain administrators group. If you are using a
Microsoft server cluster, the DSSA must run under the same
account on each node of the cluster. If you are updating or
reinstalling DSSA, the previous DSSA admin account name
is displayed here.
You must enter the Domain Account Name in the following
format: domain\user name.
Note: The installation program verifies that the account is
valid on the network, but it does not confirm that it is a
domain account or is a member of the domain
administrators group.
Type the Domain Account Name, Password, Re-Enter Password,
and then click Next.
7. The Destination Folder dialog box appears. The default
installation location is C:\Program Files\Open
Text\Document Server Sentry Agent. Click the Change
button to select a different location, if needed; otherwise,
click Next.
The DSSA should be installed on the same machine or share
as the document server. If you are using a Microsoft server
cluster, you must install DSSA on each node (member
machine) in the cluster.
8. The Ready to install dialog box appears. Click Install.
112 CHAPTER 7
7. The Shared Folder Permissions dialog box appears.
Set the kind of permissions you want for the shared folder.
Select one of the following options:
All users have read-only access
Administrators have full access; other users have read-only
access
Administrators have full access; other users have no access
Customize permissions
Note that when you set custom permissions, you are setting
permissions for the folder itself; we suggest that you set
specific permissions on the folder items themselves, if
desired.
7.1 If you click Customize permissions the Custom button
becomes available. Click Custom.
7.2 The Custom Permissions dialog box appears. On the
Share Permissions tab, click Add.
114 CHAPTER 7
5. Click Remove to remove the inherited permissions and keep
only the permissions explicitly specified on the share. Notice
that the group Everyone is removed from the list on the
Security tab.
6. In the Properties dialog box, click Add and add the group
DOCS_USERS, the DSSA admin account, and the DM
Server service account. Then click OK.
7. On the Properties dialog box, give the following permissions
to the newly added names:
DSSA admin account:Full Control
DM Server service account:Full Control
DOCS_USERS group:Modify
8. Note that when you select Modify, the boxes below Modify in
the Allow column are automatically selected.To verify that
the permission to delete files is denied to DOCS_USERS,
click Advanced; then highlight DOCS_USERS and click Edit.
The following check boxes should be cleared:
Delete Subfolders and Files
Change Permissions
Take Ownership
All other check boxes should be selected.
3 Click OK.
116 CHAPTER 7
To view a documents audit trail:
1. Select a document from the Quick Retrieve list.
2. From the Document menu, select Audit Trail. (If the Audit
Trail command does not appear, the selected document is
not stored on a DSSA document server.) A log of the activity
on the document appears.
3. When you are finished, click Close.
8
Installing RM
In This Chapter
119
Related Manuals
In addition to this manual, you will find the following documents
helpful.
RM Administration Guide Instructions on using the RM
Administration Tool for the set up and administration of
RM.
Using RM Extensions Provides detailed instructions on
using RM.
DM Designer Guide. This guide explains how you can use
the Designer application to customize the DM database by
adding tables and columns for data you need. The guide also
shows how you can design DM forms to show all data about
your document objects using the look and feel your
organization wants.
DM/RM Data Dictionary Use this manual in conjunction
with the DM Designer Guide when modifying RM forms.
In addition to these printed and online documents, each RM
component has an extensive online Help system.
Installing RM
Installation of RM is a multiple-step process that includes installation
of components in several locations.
You will install different components of RM in the following places:
DM Server: RM is a component during DM Server
installation. To install it, you must enter a valid serial
number and license key.
DM Web Server: RM is a component during DM Web
Server installation.
Records Managers: The RM Administration Tool can be
installed on any client computer that has the appropriate
SQL client and access to the DM Server.
120 CHAPTER 8
details. In brief, however, the following steps are required to install the
RM Server component along with DM Server.
1. Uninstall any previous version of RM Server.
2. Execute the eDOCS DM 5.3 Server.msi Windows Installer
Package. The Windows Installer will prepare to install.
3. When asked to provide serial numbers and passwords ,
enter your RM Server Component serial number.
4. After the DM Server installation is complete, you must run
Library Generator against your existing libraries.
To locate your libraries, Library Generator must access your
PCDOCS.INI file. During installation, you will be asked for
this files location and it will be copied to the DM Server
\Program folder.
The RM.INI configuration file is also created in the default
location C:\Program Files\Open Text\DM Server\Program.
5. The DM Server Configuration Wizard will be launched
next. Proceed with Configuring the DM Server on
page 19.
After you complete installation and configuration of DM Server and
RM Server, proceed to installation of the DM Web Server, which also
includes a RM component.
INSTALLING RM 121
Prerequisites for Installing RM Administration Tool
The RM Administration Tool is used to set up and
administer a records management system for RM. The RM
Administration Tool can be installed on any computer with
an appropriate SQL client for your database and that has
access to your DM Server and your database.
For full functionality of RM Administration Tool, your
primary group must be DOCS_SUPERVISORS.
The computer on which you install RM Administration
Tool must have access to your DM Server and your database
server, and it must have the appropriate drivers for your
database.
If you are using an Oracle database, it is particularly
important that you use the database drivers from Oracle,
not the database drivers for Oracle that are supplied by
Microsoft with Windows. To install the Oracle drivers,
install the Oracle Management and Integration installation
package (the drivers are not included with the Oracle Client
installation package) or download the drivers from Oracle.
The DM Client API and the DM API must be installed on
the machine where you are installing RM Administration
Tool.
When RM Administration Tool starts, it attempts to find the
files RM.INI and PCDOCS.INI. If it tells you that it cannot
locate one or both of these files, obtain valid copies of these
files and place them in the folder where RM Administration
Tool is installed.
122 CHAPTER 8
3. The Welcome to the Open Text eDOCS RM Admin Tool
Setup Wizard appears. Click Next.
4. The End-User License Agreement dialog box appears. Select
the I accept the terms in the License Agreement check box and
then click Next.
5. The Choose Products for Licensing dialog box appears.
Type the Serial Number and Password for RM Admin and then
click Next.
6. The Custom Setup dialog box appears.
RM.INI and When you first launch the RM Administration Tool, it will attempt to
PCDOCS.INI File locate valid copies of the RM.INI and PCDOCS.INI files. If it cannot
Locations locate these files, you should copy these files from their current location
(by default, C:\Program Files\Open Text\DM Server\Program) and
place them in the RM Administration Tool directory (by default
C:\Program Files\Open Text\RM Administration Tool).
To assign forms:
1. Run Library Maintenance.
Or, you can use DM Admin in DM Webtop.
2. Go to Groups.
3. Open Group Maintenance for a group.
4. Click Forms.
5. Select the form type in the left side and assign the form
names shown below.
124 CHAPTER 8
Form Type Form Name
Profile Entry>DOCSIMAGE PD_EPROF_IMAGE
Profile Entry>MS OUTLOOK PD_MPROF
Profile Search PD_SEARCH
Quick Retrieve PD_HITLIST
Repeat this process to assign the new forms for each group that is using
RM.
Enable Logging RM servers and RM Administration Tool can log their own operations.
By examining this, you can locate configuration errors. The log file for
RM is saved into your Windows directory as RMLOG.TXT. If there is
an existing log file for RM Administration Tool, it is saved in your
Windows directory as RMADMINLOG.TXT. To enable logging, set the
following entry in RM.INI file:
[CMSSQL]
LogToFile=1
To disable logging, set LogToFile=0.
Configure a Client To configure a client for RM Custom Reports, follow these steps:
for RM Custom 1. Install the latest version of the database manufacturers
Reports ODBC software on the client.
Important: If you are using an Oracle database, you must use the database
drivers from Oracle, not the database drivers from Microsoft that are included
with Windows. To install the Oracle drivers, install the Oracle Management and
Integration installation package (not with the Oracle Client installation
package) or download the drivers from Oracle.
2. Create a Data Source and select the appropriate driver. The
name of this data source (DSN) should be the name of the
library and should differ from the name of any other ODBC
data sources you might be using, such as DM Reports.
3. Test the DSN you just created by using an ODBC test tool.
You should be able to connect to the database and return
data from the tables.
4. Alter the ODBCDataSource key in the Library section of the
RM.INI file as shown below:
[Library RMLibrary]
126 CHAPTER 8
Chapter
9
Installing DM Extensions
In This Chapter
127
Before You Begin
Installation DM Server should be installed and configured before you install DM
Prerequisites Extensions on client machines.
Install DM Extensions
To install DM Extensions:
1. From the eDOCS Suite Installer, select DM Extensions and
click Next. This automatically starts the eDOCS DM
Extensions.msi, and determines which version to install (64-
bit or 32-bit).
Or, on the client machine, execute the eDOCS DM
Extensions.msi Windows Installer Package.
For 64-bit clients, use the eDOCS DM Extensions (x64).msi.
For 32-bit clients, use the eDOCS DM Extensions (x86).msi.
2. The Weclome to Open Text eDOCS DM 5.3 Extensions
(xXX) Setup Wizard starts. Click Next.
3. The License Agreement dialog box appears. Click the I accept
the terms in the License Agreement check box and click Next.
4. The Custom Setup dialog box appears. Select which features
will be installed. The available components are:
Windows Explorer DM Extension
Dynamic Views
Microsoft Word (version number)
Microsoft Excel (version number)
Microsoft PowerPoint (version number)
Linking
Linking in Microsoft Word
Linking in Microsoft Excel
Linking in Microsoft PowerPoint
Support for all other Cross-Application Linking
Integration Options for Other Applications
Interceptor
ODMA
128 CHAPTER 9
Microsoft Outlook E-Mail Integration
Microsoft Outlook DM Extension
DM Viewer
Client Deployment Utility
RM Extensions
DM Imaging
Click Next.
5. When you select DM Imaging and/or RM Extensions, the
Add-Ons License Validation dialog box appears.
Type the Serial Number and Password, and then click Add for
each component requiring validation. The components will
appear in the Selected Licensed Add-on Product(s) pane.
Click Next.
130 CHAPTER 9
Use Library Maintenance or DM Admin in DM Webtop to configure
application integration. See the DM Administration Guide for
instructions.
Removing DM Extensions
Remove DM Extensions through Control Panels Add or Remove
Programs.
10
Installing the eDOCS DM API
In This Chapter
131
Installing eDOCS DM API
To install eDOCS DM API:
1. Execute the Open Text eDOCS DM API.msi Windows Installer
Package.
2. The Welcome to Open Text eDOCS DM API Setup Wizard
appears. Click Next.
3. The End-User License Agreement dialog box appears. Select
the I accept the terms in the License Agreement check box and
then click Next.
4. The Destination Folder dialog box appears. The default
installation location is C:\Program Files\Open Text\DM
API\. Click the Change button to select a different location, if
needed; otherwise, click Next.
5. The Ready to install dialog box appears. Click Install.
6. The Completed the Open Text eDOCS DM API Setup
Wizard appears. Click Finish.
Removing DM API
Remove DM API through Control Panels Add or Remove Programs.
132 CHAPTER 10
Chapter
11
Configuring eDOCS Imaging
In This Chapter
133
Installing the IIDS
The IIDS is installed as part of the DM Web Server software and should
be installed on each DM Web Server that will host Imaging clients. You
must provide a separate license number to install this software.
134 CHAPTER 11
The following table describes the options available in the Configuration
Manager.
Option Description
Location Reports the currently assigned root directory for
the Internet Imaging Servers cache. This
directory must exist before the server runs.
Click the Browse button to select another
directory for the cache.
Important: If you change the cache root after the
server has written files to the old location, the old
files will be orphaned and will not be used. You
can move the entire directory structure to the new
location or allow the server to rebuild the cache
through normal use.
Fill Percent Specifies the maximum percentage to which the
cache drive can be filled before the server starts to
purge older documents. Documents cannot be
purged until after they are written to the DM
library.
Thumbnail Detail Specifies the relative size and resolution of the
thumbnail images that are sent to Imaging.
Low creates the smallest, least detailed thumbnails.
The small thumbnail files are transferred most
quickly to Imaging.
Medium is a balance between transfer speed and
clarity of the resulting thumbnail.
High creates relatively high resolution thumbnails
that may be readable in the viewer, but that will
require the most time to download.
4 When you have set the options, click OK to close the TIFFServer
Configuration Manager and apply the changes.
136 CHAPTER 11
Set Internet Perform the following steps to enable ActiveX controls and plug-ins in
Explorer Security Internet Explorer.
Options 1. Run Internet Explorer.
2. Click Tools>Internet Options.
3. Go to the Security tab and click Custom Level.
4. Scroll down the list to find and enable these two entries:
Initialize and script ActiveX controls not marked as safe for
scripting
Run ActiveX controls and plug-ins
5. Click OK to accept the changes and return to the options
dialog box.
6. Click OK to close the options dialog box.
Enable Plugin in To enable the use of the browser plugin, you must enable it in the DM
DM Webtop Webtop.
1. Lauch your browser and log onto to DM Webtop.
2. Go to the My Options page.
3. Go to the Display Options tab.
4. Scroll down to find the eDOCS DM Plugins heading.
5. Select the eDOCS Imaging check box.
6. Click the Save your changes button on the toolbar.
After these two options are set, Imaging will communicate through the
plugin if it is launched by opening a document from the Webtop, and it
will communicate with the server through Application Integration if it
is launched directly from the Windows desktop or by opening a
document from DM Extensions.
12
Pointing a Component to a
Different DM Server
In This Chapter
139
Running the DM The DM Connection Wizard guides you through selection of the DM
Connection Wizard Server used by the specific DM component.
If your organization employs a multiple-server cluster for failover and
load-balancing (FOLB) purposes, the connection wizard also lets you
display the FOLB server list for the selected server. (See the DM
Administration Guide for more information on the FOLB facility.)
The wizard also allows you to remove a DM Server from an FOLB
server cluster to make it a dedicated Indexer server.
Note: If you have uninstalled DM Server from the machine where you want to
run the wizard, the wizard will fail, because shared files where removed during
the uninstall process. If this happens, reinstall DM Server.
140 CHAPTER 12
To run the wizard:
1. Select Start>Programs>Open Text>DM Connection
Wizard.
2. On the Specify DM Server page, enter the name of the server
machine that the component will initially log on to. DM
Servers that you have logged on to in the past are shown and
you can select one from the list.
5 The server list associated with the server you selected on the
previous page is displayed. The option Enable FOLB should be
selected. Click Finish to exit the wizard.
141
142 CHAPTER 12
APPENDIX
A
Setting Up the DM Server
Service Account
In This Appendix
143
About the DM Server Service Account
The DM Server service requires network access, so it must be run under
an account that has the following privileges and abilities:
Access to the network and to all document servers,
libraries, and SQL databases. The DM Server service
account is not required to be a domain account, but we
strongly recommend that you make it a domain account
because it must typically access data on other network
resources.
"Act as a part of the operating system" rights. This privilege
is set up for the DM Server service account by the DM
Server Configuration Wizard.
"Log on as a service" rights. This privilege is set up for the
DM Server service account by the DM Server Configuration
Wizard.
Membership in the local administrator group on the local
machine. The account need not be a member of the Domain
Admins group.
Full Control rights to the document storage location on
each document server. Permissions should be applied at the
last static directory in the document path template.
Membership in the DOCS_SUPERVISORS group in every
DM library and at the NOS level. In the library, the
accounts Primary Group must be DOCS_SUPERVISORS.
The DM Server service account must be created prior to installing the
DM Server software. During installation, the DM Server Configuration
Wizard will grant the Act as part of the operating system and Log on
as a service rights, if the account does not already carry them.
144 APPENDIX A
Creating the To set up the DM Server service account on a Windows 2000
Account Server machine:
1. Go to the Start menu and click Programs>Administrative
Tools>Computer Management.
2. In the tree, expand the Local Users and Groups node, right-
click Users, andthen select New User.
3. Enter the User name and Password of the account. Enter a
description, such as DM Server Service Account, if you like.
Then select the password option appropriate for your
organization. Click Create and then click Close. The new
account is shown in the user list in the Computer
Management windows.
B
Special Considerations for
Microsoft SQL Server Libraries
In This Appendix
149
Installation Impact on Regular Operations
During installation you are required to stop and restart the system to
load certain programs that SQL Server installs. If you are installing SQL
Server on a system accessed by users during the daily operations of your
business, schedule the installation for a time when users are off the
system.
150 APPENDIX B
Support for Microsoft SQL Server 2005
To enable support for Microsoft SQL Server 2005, you need to use a
complex password the first time you run Library Generator. A complex
password is a password that:
Does not contain the users account name, either in full or
in part.
Is at least six characters in length.
Contains characters from three of the following categories:
English uppercase characters (A through Z).
English lowercase characters (a through z).
Numbers (0 through 9).
Non-alphanumeric characters (for example: !, $, #, %).
After running Library Generator, you can disable password policy
enforcement. Refer to your SQL documentation for additional
information.
Document Servers A document server is the location where documents are stored. A
document server consists of a file server and storage location. It does
not use SQL Server. DM supports several operating systems as
document servers. See the release notes for a list of the operating
systems supported for your installation.
Database Servers SQL Server resides on the database server. A database server can
contain one or more SQL databases.
In DM, the SQL database contains the tables and columns that make up
a DM library. The library contains information about each document,
stored in a record called the Document Profile. The profiles contain
pointers to the physical documents, which are stored in their native
format on the document server(s).
LAN Environments If your installation requires multiple libraries, be aware that each SQL
server will need to provide sufficient user connections to permit access
by users from other SQL servers. Memory requirements for the SQL
server increase with the number of connected users. With Microsoft
SQL Server, you have the option of allocating memory dynamically,
based on demand, rather than setting a fixed amount. If you choose to
152 APPENDIX B
manage memory in this wayand we recommend you doset the
number of user connections to zero (0). This will allow SQL Server to
create user connections on demand. By default, the number of user
connections is set to zero when you install SQL Server. See User
Connections on page 159 for more information.
WAN Environments In a large organization with multiple locations, each physical site
should have its own database server(s). Having to connect to another
city to search for information about documents stored in the local city
would create heavy network traffic between the locations.
In smaller organizations, or those with few offsite users, a single
database server may be preferable, because a centralized setup may
reduce the time and cost of administration.
As in a LAN environment, you will need to provide sufficient memory
so that SQL Server can open user connections for users from other SQL
servers.
SQL Server and The various SQL Server files and amount of space needed for each are
System Files as follows:
SQL Server Program Files and System Databases: In
addition to the program files, SQL Server maintains four
system databases for each instance (master, model, msdb,
and tempdb), which expand automatically as needed.
Altogether, these files need a minimum of 100 MB of disk
space.
SQL Transaction Log: For the transaction log, you need to
reserve enough disk space to store the maximum amount of
transactions that can occur between backups. Typically,
providing space equivalent to 30 to 50 percent of the size of
the database is sufficient. If a transaction log runs out of
space, users will be unable to perform database transactions
until the log is dumped.
Note: The transaction log records database transactions as they are
DM Database To determine how much space you will need for a DM database,
calculate the amount of space necessary for information on existing
documents plus at least one years worth of growth. There are many
items for which you need to provide space in a database.
N x 1KB = A
or
154 APPENDIX B
Use a per-period estimate. Determine how many documents
are created each day, week, or month. Then multiply this
number by the associated number of periods per year. For
example, if you estimate that approximately 10 new
documents are created every day, and there are 260 work
days in a year, you could estimate that 2,600 documents
would be created in the coming year.
Once you develop a reasonable estimate of the number of documents
to be created in the next year, multiply the number by 1 KB to
determine the database space that many new documents will require.
You can use this formula:
N x 1KB = B
where N is the number of new documents and B is the space required
for the new documents in kilobytes.
Records for Activity on Documents
Each document record (whether imported or created) grows as the
document is edited and new versions are created. You should allocate
roughly the same amount of database space for activity on documents
as you provide for new documents.
156 APPENDIX B
character, date, and integer fields. Heres how to estimate the space
required:
Character-type columns occupy 1 byte of space per
character. For each custom table, count the number of
character-type columns and add up their total length to
estimate the maximum amount of space the character
columns could occupy in each record.
Date-type columns occupy 8 bytes of space. For each
validation table, count the number of date-type columns
and multiply that number by 8 to determine the amount of
space all date columns will occupy in each record.
Integer-type columns occupy 4 bytes of space. For each
validation table, count the number of integer-type columns
and multiply that number by 4 to determine the amount of
space all integer columns will occupy in each record.
Note: Each table is assigned a SYSTEM_ID by DM. The
SYSTEM_ID is always an integer type. Any foreign key
associations are also integer types. For more information
about building custom tables, refer to the manual DM
Designer Guide.
For example, say you work in a research environment where it is
necessary to track information about multiple research grants. Each
document in the library is associated with a particular grant. A custom
table called GRANTS, illustrated below, records the source of the grant,
a description of the purpose of the grant, and the beginning and ending
dates of the grant. The account manager and primary researcher, whose
information is stored in the PEOPLE table, is also recorded in the table.
Grants Table
The maximum amount of space occupied by all the fields is 258 bytes.
This means that approximately four grant records will occupy a
kilobyte of space.
To estimate how much space the table will occupy, you would first
determine the number of grants. Then divide the total number of
grants by the number of grants per kilobyte (in this case, four) to
determine the amount of space required in kilobytes.
Memory Requirements
SQL Server uses memory to manage users, databases, database objects,
and locks. Any additional memory is used for procedure and data
cache. Increasing the memory available to SQL Server can improve
performance.
With Microsoft SQL Server, you have the option of allocating a fixed
amount of memory or allowing SQL Server to configure memory
dynamically according to demand. We recommend you choose the
latter option. (If you want to allocate memory for user connections, see
User Connections on page 159.)
Even if you allow SQL Server to configure memory dynamically, you are
still faced with the question of how much memory to provide on the
server machine.
158 APPENDIX B
If additional memory is available and the activities requested by the
user connection require it, SQL Server can allocate additional memory
to a connection. Typically, providing enough memory to cover twice
the number of users will be sufficient. If you allow SQL Server to
allocate memory on demand, any unused memory will be released for
functionality elsewhere in the server machine.
(U 80)/1024 + 12 = Z
If you want to manage the memory options for SQL Server, see SQL
Server Books Online.
User Connections
A user connection allows a DM user to connect to the SQL server and
execute a transaction.
160 APPENDIX B
Performs a table lookup, as when searching for an author
name or document type.
For a launched module, the connection stays open as long as the
module is open. For a table lookup, the connection is released once the
user has selected an item from the lookup table.
DM: A single connection can be used for multiple user transactions.
Note: The number of user connections is different from the number of licenses
you have for SQL Server. Licenses are determined by your arrangements with
Microsoft. User connections can be increased as needed, provided the SQL
server has the memory to support them.
Server Complete one worksheet per SQL server. If you have questions, fax the
Configuration worksheet with your information to Open Text Technical Support for
Worksheet assistance at (850) 942-8085.
162 APPENDIX B
SQL Server Record the following information prior to installing SQL Server. Keep
Installation the completed list for your records.
Worksheet 1 Windows and SQL server names:
____________________________________________________
____________________________________________________
2 SPX/IPX server name (if applicable):
____________________________________________________
3 TCP/IP file address or host name (if applicable):
____________________________________________________
4 TCP/IP port number (if applicable):
____________________________________________________
WORKSHEETS 163
Database The following information should be completed for each database.
Configuration 1 Unique library database name:
Worksheet
____________________________________________________
2 To complete the following information, see DM Database on
page 154.
164 APPENDIX B
Installation Complete this worksheet during the installation of SQL Server.
Worksheet 1. Client-licensing mode:
Per server. Number of concurrent connections allowed:
___________
Per seat. Use License Manager to record the number of
licenses. ___________
2. SQL Server installation drive and directory. The default is
C:\Program Files/Microsoft SQL Server.
_______________________________________________
3. Character set:
ISO character set (default)
850 Multilingual (Western European languages)
437 U.S. English
Other : _____________________________
For example:
1250 Latin2 (Eastern European languages)
1251 Cyrillic Slavic (Russian and other Slavic languages)
1253 Greek
1254 Turkish
1255 Hebrew
1256 Arabic
4. Sort order. Choose one of the following. We recommend
dictionary order, case-insensitive. Do not choose a binary or
case-sensitive sort order.
Dictionary order, case-insensitive
Dictionary order, case-insensitive, uppercase preference
Dictionary order, case-insensitive, accent-insensitive
5. Network support. Choose one or more of the following:
Named Pipes (must be selected)
NWLink IPX/SPX
TCP/IP Sockets
Other: _____________________________
WORKSHEETS 165
6. NWLink IPX/SPX service name. The default is the name of
the server computer.
_______________________________________________
7. TCP/IP port. The default is 1433, although you have the
option of allowing SQL to determine the port number
dynamically.
_______________________________________________
8. Startup options. Choose one or both options. (We
recommend you select both.)
Autostart SQL Server at boot time
Autostart SQL Server Agent at boot time
9. SQL Executive user account.
_______________________________________________
166 APPENDIX B
APPENDIX
C
Special Considerations for
Oracle Libraries
In This Appendix
165
DM Requirement for Oracle Databases
Prior to generating a DM library, an Oracle instance and a database
must exist. The instance/database may be created expressly for the
library or an existing instance/database may be used.Running in
ARCHIVELOG Mode
Running the library database in ARCHIVELOG mode allows Oracle to
compile a complete transaction record, which can be used to restore the
database in the event of a failure
Because library generation creates many tables and rows, we
recommend you remove the database from ARCHIVELOG mode prior
to running Library Generator. This will speed up the generation
process. Once library generation is complete, return the database to
ARCHIVELOG mode.
Tablespace Names Unless you assign your own tablespace names, the default tablespace
names assigned during library generation are incremented for each
166 APPENDIX C
new library on an instance. For example, for the first library, the default
tablespace names are DOCSPROF, DOCSVAL, DOCSIND, and
DOCSTMP; for the second library they are DOCSPROF2, DOCSVAL2,
DOCSIND2, and DOCSTMP2. Up to 100 libraries can be created using
the default tablespace names.
Selecting Mixed- When you generate a new libraryor upgrade an existing onewith
Case Storage DMs Library Generator, a dialog box appears during the generation
During Library process. The dialog box asks if you want the library to support mixed-
case data.
Generation
To store data in mixed case, click Yes; to store data in uppercase only,
select No.
If you select Yes, DM creates the uppercase indexes for the searchable
text fields on the Profile form.
INIT.ORA These settings must be present in the INIT.ORA file to support the
Modifications for Function-Based Indexes feature:
Mixed-Case Data QUERY_REWRITE_INTEGRITY=TRUSTED
QUERY_REWRITE_ENABLED=TRUE
COMPATIBLE= 8.1.0.0.0 (or greater)
To have these settings take effect, restart the Oracle instance.
Removing Indexes When you upgrade a library that was previously generated without
to Improve mixed-case data, DM does not remove the non-functioned indexes
Performance (that is, the indexes formerly used to support searching). To improve
search performance, we recommend you remove those indexes from
your database. The table below lists the old index names along with the
uppercase indexes that are created when you generated the library for
mixed-case data.
168 APPENDIX C
Old Index/
Table Column Uppercase Index Unique
APPS APPLICATION APPSC1 YES
UPPER(APPLICATION) APPSCU
DBIMPORTIGNORE IGNORE_TEXT DBIMPIGNOREC1 YES
UPPER(IGNORE_TEXT) DBIMPIGNORECU
DOCSERVERS LOCATION DOCSERVERSC1 YES
UPPER(LOCATION) DOCSERVERSCU
DOCUMENTTYPES TYPE_ID DOCTYPESC1 YES
UPPER(TYPE_ID) DOCTYPESCU
GROUPS GROUP_ID GROUPSC1 YES
UPPER(GROUP_ID) GROUPCU
PEOPLE USER_ID PEOPLEC1 YES
UPPER(USER_ID) PEOPLECU
NETWORK_ALIASE NETWORK_ID,NETWORK_T NETWORK_ALIASES YES
S YPE 1
UPPER(NETWORK_ID),NET NETWORK_ALIASES
WORK_TYPE U
REMOTE_LIBRARIE LIBRARY_NAME REMOTE_LIBSC1 YES
S
UPPER(LIBRARY_NAME) REMOTE_LIBSCU
KEYWORD KEYWORD_ID KEYWORDC YES
UPPER(KEYWORD_ID) KEYWORDU
PROFILE DOCNAME PROFILENAME YES
If doc names unique UPPER(DOCNAME) PROFILENAMEU
PROFILE DOCNAME PROFILENAME NO
If doc names not UPPER(DOCNAME) PROFILENAMEU
unique
STOPWORDS STOPWORD STOPWORDSC1 YES
UPPER(STOPWORD) STOPWORDSCU
Financial Libraries:
170 APPENDIX C
%TS_NAME% indicates the tablespace name
%KEY_LEN <number>% indicates the key length variables.
D
The PCDOCS.INI File
In This Appendix
This appendix notes the PCDOCS.INI file settings that are applicable
to DM. Settings not listed here are applicable only to DOCSFusion or
DOCS Open.
173
Location
When you install the DM Server software, the setup program asks for
the location of your existing PCDOCS.INI file and copies it to DM
Server\Program directory (by default, C:\Program Files\Open
Text\DM Server\Program). Library Generator creates a PCDOCS.INI
file in this directory if it does not find one already there.
After library generation, you can copy the file to another location if
necessary. If you decide to move the file after installation, you will need
to run Server Manager and identify the files new location. See the
chapter entitled Setting DM Server Properties in the DM Administration
Guide for instructions.
Settings
The following settings in the PCDOCS.INI file are used by DM.
Settings not listed here are ignored by DM.
[Library <library name>] Section
Vendor: The SQL vendor number (Microsoft SQL
Server=3,Oracle=5, Sybase=6)
Database: The name given to the DM database during installation
of the SQL engine.
Location: The name of your SQL server.
Username: The common login name for users to access the DM
database.
Password: The password for the common login.
DefaultDOCServer: The document server on which documents
are stored by default.
Owner: If the library is on an Oracle 8i or higher database, this
field contains the account name of the library owner. (When
multiple libraries are stored on a single Oracle instance, they are
differentiated by owner account.)
UseDocnameInFolderContents: Selects whether document
names or display names are shown in DM Webtop for folders on
174 APPENDIX D
the Folder Contents and Public Folders pages and for workspaces
on the Workspaces page. Folders and workspaces are assigned a
document name (specified on the Document Profile form) as
well as a display name (specified on the Update Properties
dialog box). If UseDocnameInFolderContents is set to 1,
document names are displayed; if the setting is 0, display names
are shown. If you choose to have display names shown, we suggest
you notify users that changes to document names on the
Document Profile will not be reflected on display listings such as
the Folder Contents page.
[LDAP] Section
ServerLocation: Points DM Server to the location of the
Lightweight Directory Access Protocol (LDAP) server so that
LDAP names can be used for authentication.
ServerLocation=//<ldap><:port>/o=<....>,c=<....>
where:
<ldap> is the DNS name for the host of the LDAP service.
<port> is the port number of the LDAP server. Inclusion of
the port number is optional. If you do not include the port
number, you should omit the colon (:) also.
o=<....>,c=<....> is the root context for the LDAP directory.
For example:
ServerLocation=//ldap.server.com:389/dc=mycompany,dc=com
[Network] Section
DriveUnmapTries: This setting addresses an issue where drive
mappings created during a DM process (such as Document
Import), which are intended exist only for the duration of the
process, are not being released because high network activity
delays completion of the process beyond the instruction to release
the drive mapping. This setting causes successive calls to be made
to release the drive mapping until one of the calls succeeds.
DriveUnmapTries=<number>
where <number> is the number of calls that will be made to
release the drive mapping until a call succeeds. Any value between
SETTINGS 175
1 and 30 may be used. If this setting is not added to the
PCDOCS.INI file, the default is 4.
176 APPENDIX D
APPENDIX
E
Troubleshooting
In This Appendix
This appendix describes how to resolve issues that may arise during
setup or administration of DM.
179
Accessing Our Knowledge Base
Descriptions of a number of issues related to setup and administration
of the DM Suite can be found in Open Texts online Knowledge Center.
If you have a problem, we suggest you search the Knowledge Center for
items that may be pertinent to your installation. If you cannot resolve
the problem after looking in both this chapter and the Knowledge
Center, contact Open Text Technical Support for assistance.
Check the Setup of the DM Server Service Account ........................... 180
The Accounts Status on the Network....................................... 181
DCOM Points to the Account on Server..................................... 181
DCOM on DM Client Machines Points to the Account............... 181
Changes to the Service Account ................................................ 181
Problems Locating DM Server............................................................. 182
Cannot Locate DM Server........................................................... 182
Local Server Not on FOLB List .................................................... 182
NetWare Connectivity ......................................................................... 182
Unable to Connect to NetWare Document Servers .................. 182
Miscellaneous Issues........................................................................... 183
DM Server Will Not Start and DCOM Errors Reported ............... 183
Cant Start Message Appears After Reboot ........................... 183
Changes Made in DM Server Admin Tools not Reflected on Clients
184
DCOM Errors Related to SearchServer ....................................... 184
180 APPENDIX E
The Accounts Status on the Network
Windowsonly networks and organizations with mixed NetWare
and Windows networks: the service account must be set up as a
network domain account, not a local machine account.
NetWare-only systems: the service account must be a local
account.
DCOM Points to the Account on Server
Ensure that DCOM is pointing to the DM Server service account on the
network and not to the server machines local system account. By
default, many services run as a local system account. If the account is
local, there may be problems with clients connecting to the server.
DCOM on DM Client Machines Points to the Account
Verify that the DM Server service account is properly identified to
DCOM on DM client machines (DM Web Server and workstations of
users running application integration and DM Extensions):
10. Select Start>Run and then type DCOMCNFG. Click Services.
11. Highlight Open Text eDOCS DM Server, right-click and select
Properties.
12. Click the Log On tab. Verify that the This account option is
selected and that the user name and password are those of
the DM Server service account. The user name must be in
the format:
domain name\account name
In DCOM configuration, you do not need to select the DM Server service
account under This account on DM client machines.
Changes to the Service Account
When making changes to the DM Server service account, such as
changing the password or identifying a different user as the service
account, we recommend you follow this procedure:
1. If you are changing a property, such as the password, make
the change at the network level.
2. Make the change in DCOM by running DCOMCNFG. This
will also update the service. Do not change the service via
the Control Panel. This is handled automatically when you
modify the account via DCOMCNFG.
NetWare Connectivity
Unable to Connect to NetWare Document Servers
First, verify that the Novell NetWare Client for Windows is installed on
the DM Server machine. Open Text does not support the use of the
Windows client for NetWare.
Then look at the NetWare Servers tab in the DM Server Manager for the
following items pertaining to the DM Server service account:
182 APPENDIX E
The NDS Tree Name field should contain only the tree
name, not a backslash or any other character.
The NDS Context field should display only the container
associated with the DM Server service account (or the DM
Server account name) and all parent containers to that
container. Do not include the tree name.
The User Name field should display only the user name of
the DM Server service account. Do not include container or
tree names.
For example, the following screen capture from NetWare
Administrator illustrates the organizational hierarchy in which a DM
Server service account (for example, DMadmin) is a member.
Miscellaneous Issues
DM Server Will Not Start and DCOM Errors Reported
In the Windows 2003/2000 Control Panel, select Services and look at
the Startup options listed for DM Server. In the Log On As box, verify
that This Account is selected and that the DM Server service account
name and password are shown.
If the DM Server service account is selected on the Startup options and
you are still getting DCOM errors, click OK on the Service dialog box
and exit the Control Panel. Then reenter Control Panel>Services, click
Startup, and click OK on the Service dialog box again. Sometimes just
reinforcing the options on the Service dialog box can correct the
problem.
Cant Start Message Appears After Reboot
Messages that the DM Server service cannot be started can be generated
following a reboot when DM Server and the SQL server reside on the
same Windows machine. Once the reboot finishes and you run Server
Manager, you will see that the DM Server service has started after all.
The message appears because DM Server is dependent on other
services, such as the SQL server service. If on reboot, the other services
take longer to restart than DM Server, you will see the cant start
message as well as messages in the system and application logs. DM
184 APPENDIX E
1. Edit the following key in the registry:
HKEY_LOCAL_MACHINE
SOFTWARE
Hummingbird
DOCSFusion
2. Highlight the value MaxDBProcesses and click
Edit>Modify. In the Value data field, enter the number of
connections for your system. The value can be in either
Hexadecimal or Decimal format; select the corresponding
Base button.
3. Stop and restart the DM Server service.
Note: Increasing the number of database connections may require additional
memory.
See the topic Insufficient Disk Space in SQL Books Online for
instructions on recovering from this error and preventing future full-
database problems.
Error #10004 Error #10004 indicates that there is a problem connecting to the server.
Verify that the network is working properly and SQL Server is running.
186 APPENDIX E
Decreased There are several things you can do to improve performance on a slow-
Performance or running machine:
High Server Use the DBCC (database consistency checker) statements to
Utilization make sure that nothing is wrong with the database. See
your Microsoft documentation for instructions on using the
DBCC statements.
Run the UPDATE STATISTICS command. This will correct
any slowness caused by the SQL server choosing less than
optimal paths for retrieving data. See your Microsoft
documentation for instructions on running the UPDATE
STATISTICS command.
Users who perform unqualified searches (searches returning
all documents in a library) can slow the server dramatically.
A flag can be set in the servers PCDOCS.INI file to prevent
users from executing unqualified searches. To do this, add
the following to the PCDOCS.INI file:
[QBESearch]
AllowUnqualifiedSearches = 0
188 APPENDIX E
Index
C about 108
audit trail 116
Changing Database Access from Trusted
Connection 65 configuring 115
creating a share 112
D document server configuration 115
database administrator login and installation 110
password 37, 41 requirements 109
databases. See libraries. document servers
DM Server defining 56
installing 17 importing existing documents into 64
prerequisites for installation 16 documents
DM Server service account defining document servers 56
creating on Windows 2000 146 importing into document servers 64
rights required 146 Profiles 151
DM Web Server
installing 24 E
prerequisites for installation 23 eDOCS RM
DM WorkFlow additional installation information 124
common file locations 85 assigning forms 124
enabling mail notification 84 configuring for custom reports 125
installing 83 enable logging 124
on DM Web Server 90 installing
server components 86 on DM Web Server 121
web server information 83 RM Administration Tool 122
library requirements 84 server components 120
post-installation setup 90 PCDOCS.INI file location 121, 124
single library restriction 84 repair option 126
user synchronization 88 uninstalling the RM Administration
WorkFlow Engine requirements 84 Tool 126
DOCSADM login and password 41, 168 eDOCS Suite Installer 14
Document Sentry Agent error recovery 185
INDEX 189
G M
groups, adding local to DM library 97 Microsoft SQL Server
disk space requirements for library 154
I disk space requirements for server files 153
location of libraries 152
IIS Anonymous User account 83
location of transaction logs 152
indexing with DM Indexer
locations of SQL and data files 150
index location 72 memory for user connections 159
index log files 77 memory requirements 152, 158
index properties 72 multiple libraries 152
multiple indexes for single library 78 user connections 152
installation user-connections 160
DM Server 17 Windows service accounts 150
DM Web Server 24 MSI Install Options 7
Document Sentry Agent (DSA) 110 MSI Silent Install Samples 11
Windows Security Service 93
N
L network aliases, synchronizing with the
library 61
libraries
about 151 O
adding users to 61 Oracle
custom tables for industry types 35 adding rollback segments to INIT.ORA 63,
populating with your data 64 64
SQL database administrator login and creating a new tablespace 51
password 37, 41 creating a temporary tablespace 53
library generation database owners 168
activities required after 64 editing tablespace storage parameters 48
activities required prior to 30 improving search performance 170
instructions for updating 32 modifications to INIT.ORA 169, 170
modifying a default tablespace 50
logins and passwords
owners of multiple libraries on an
database administrator 37, 41 instance 41
DOCSADM 41 prerequisites for library generation 169
Microsoft SQL Server service accounts 150 rollback setments for multiple libraries 169
Oracle database owner 168 specifying number of redo log files 55
190
specifying number of rollback segments 54, W
63, 64
Windows
specifying tablespaces 44
DSA requirements 109
speeding up the library generation
process 168 Windows Security Service
tablespace names 168 configuring a document server 104
installing 93
troubleshooting client connection to
database 187 starting and stopping 105
troubleshooting 106
P
PCDOCS.INI file
location 176
location of 31
settings used by eDOCS DM 176
performance, improving 187
S
Scripted Installs 7
security
Document Sentry Agent (DSA) 108
Services 11
SQL client software, installing 3
T
Transforms 6
troubleshooting 179
U
uninstalling RM Administration Tool 126
users
adding to libraries 61
synchronizing network aliases 61
Using Mixed and Windows
Authentication 65
INDEX 191