Server Installation - windreamdownload.windream.com/wd40/dokumente/serversetup-e.pdf · Basics of...

windream

Server Installation

windream GmbH, Bochum

Copyright © 2001 – 2007

bywindream GmbHWasserstr.21944799 Bochum

Issue: 08/07 – 4.0.0.0

All rights reserved. No part of the contents of thisdescription may be reproduced or transmitted in any form(print, photocopy, or any other form) or by any meanswithout the explicit written permission of windreamGmbH.

Important NotesAll information and technical specifications in this description have beencollected by the authors with great care. They cannot, however, eitherguarantee, take legal responsibility or make any other warranty for theresults of the use of this information.

We would also like to point out that all software and hardware brand namesin this desription are the exclusive property of the trademark, brandname orpatent right holders. This are naturally protected by the appropriate lawsand trade agreements.

Table of Contents I

Table of Contents

1 windream Server Installation

Installation of the windream Server services 1-1Important warning concerning setup 1-1

Restricted path length in the system environment 1-1Basics of the windream server installation 1-2System requirements 1-3

Client – server system architecture 1-3Designator of the domain 1-4System requirements of the windream services 1-4System requirements of the windream database 1-6System requirements hard disk drive 1-9

Installing the windream ObjectStore 1-10Access permission for the windream mainuser 1-10

Further requirements 1-11Creating windream group accounts 1-12Configuring windream user accounts 1-14

Creating the windream mainuser account 1-14windream - common user account configuration 1-15

MS SQL Server authentication 1-19Possible authentication modes 1-20

Oracle authentication 1-21Installing the windream server (starting the setup program) 1-22

Language version 1-22Starting the setup program 1-23Software licence agreement 1-23Information on system requirements 1-23Type of setup 1-23Selecting components (user-defined only) 1-24windream database type 1-25Updating system libraries 1-26Installing the database 1-26windream user authentication 1-27Licensing 1-28Select destination folder 1-29windream TDI-settings 1-29windream ObjectStore presettings 1-30windream directories for file storage 1-31windream database 1-35Oracle database settings 1-38Oracle CTXSYS login 1-39windream user / group configuration 1-40

II Table of Contents

Select program folder 1-44SQL Server authentication 1-44Oracle authentication 1-45Start copying process 1-46Starting the windream services 1-47setup complete 1-47

During the installation 1-48Installation complete 1-48

Viewing logfiles 1-49Starting the windream services 1-49Oracle job for fulltext indexing 1-49

Installation check 1-49Checking whether windream services have been started 1-50Checking the windream setup log 1-50List of windream server logfiles and diagnostic outputs 1-51

2 windream Server Basic Configuration

Basic windream Server Settings 2-1Basics 2-1

Further requirements for operating windream 2-2Operating system rights for the windream mainuser 2-3DCOM configuration for windream DMS service and thumbnailservice 2-4

Tab page 2-5Location 2-5Tab page Security 2-6Tab page Identity 2-11Closing the DCOM configuration dialog 2-13

Adjustments in the administration - services 2-14Adjustments in the 2-17windream configuration 2-17

Tab page Connections 2-20Tab page Filter 2-20Tab page Licences 2-22Tab page Fulltext 2-22Tab page Common 2-23

Settings for scheduled tasks 2-25SQL Server schedule for fulltext population 2-25

Creating a new schedule 2-26Remote index update under SQL Server 2000 2-30

Oracle jobs for fulltext indexing 2-31Assigning windream rights to root directory 2-32

Table of Contents III

3 windream Server Uninstallation

Uninstalling the windream Server Services 3-1Uninstalling the ObjectStore service 3-1Uninstall windream server services 3-1

Uninstalling the windream server services 3-3

4 Important Notes on Installation and Configuration

User account for executing the installation 4-1No connection to server (unknown error) 4-1Context menu unavailable on windream client computer 4-1Error while executing file WMInit.exe 4-2Changing the assignment of users to groups 4-2windream DMS service not started 4-2

Incorrect windream mainuser 4-2Incorrect setting of DCOM configuration / administration -services 4-4ObjectStore service not configured or not started 4-4windream mainuser unknown to the ObjectStore service 4-4Incorrect windream database name 4-4

IP server address changed 4-4Oracle DB instance not yet accessible 4-5Database not correctly installed 4-6windream TCP-service does not start (WSAADDRINUSE) 4-8Invisible domains or users/groups of domains 4-10Changing the user ID (name / password) of the windream mainuser 4-11Enhancing the SQL Server database performance via the Named Pipesprotocol 4-17

5 windream Server Update Installation

windream Server Services Update Installation 5-1Basic requirements for an update installation 5-1

Notes on migration from windream 3.0 to windream 3.5 or 3.6 5-1Further requirements 5-1Closing the windream services 5-2

Updating the windream server 5-4Starting the setup program 5-4Security question before executing the setup program 5-4Selecting components 5-4Installing the database 5-5

IV Table of Contents

windream database type 5-6windream licensing 5-6Updating the windream database / database fulltext extension 5-7Oracle database settings update 5-9Oracle CTXSYS login - update 5-9SQL server authentication 5-10Oracle authentication 5-11Start copying process 5-12Setting the start type of the windream services and starting theservices 5-13Update complete 5-13

Updating the windream main services and the windream fulltext service5-13List of update logfiles and diagnostic outputs 5-16

6 Annotations

Table of Figures 6-1

Table of Charts 6-3

Index 6-5

winwinwinwindreamServerServerServerServer

InstallationInstallationInstallationInstallation

1

Important warning concerning setup 1-1

Installation of the windreamServer services

Important warning concerning setupBefore starting the installation of the windream Server services, pleaseurgently consider the following important warnings.

Restricted path length in the system environment

Important note: If during the server setup the maximum lengthof the path (1023 characters) is exceeded in the systemenvironment, setup will display a respective message and cancel theinstallation process.

Thus, please check the length of the path variable ("PATH")before each windream server setup (incl. update) over thecommandStart>Settings>Control Panel>System Environment. In thedialog box named System Properties (tab page Advanced), you selectentry PATH from the environment variables.

For being able to check the path length, windream GmbH offers atool named "wmckpath.exe" for being downloaded from theInternet addresshttp://www.windream.com.With this tool, you can check the current length of the path and therespective path entries of your system.

If the path length is not longer than 800 characters, the windreamServer can be installed without any problems. However, if thelength exceeds the number of 800 characters, please check first, ifthe path can be shortened (for example by deleting double entries).

If the path cannot be shortened, you will be unable to installthe windream Server services!

1-2 Basics of the windream server installation

Basics of the windream server installationThis installation description serves as a guideline for the installation ofthe windream Server services.

Specific configurations are executed automatically by the setupprogram during the installation of the windream Server services (forexample creation of the windream group accounts). The followingsettings are made by the setup program:

• Creation of the windream group of all windream users.• Creation of the windream mainuser account (if not available yet)

and assignment to the local administrator group.• Assign required operation system rights ("Login as Service", "Login

as Batch Processing Job", and " Act as Part of Operating System")to the windream mainuser.

• Set DCOM Configurations for the windream Services named DMS-Service and Thumbnail Service.

• Set the windream Server services (DMS-Service, Thumbnail Service,Event Service and Full-text Service) in the system settings (theservices will not be started by the setup program).

• Create SQL Server schedule for full-text population.

An additional dialog box is offered in the setup program for theconfiguration and the creation of the windream mainuser and thewindream group of all windream users. All other settings which areautomatically executed by the setup program do not require anyadditional entries.

Please cf. the respective notes in the chapters of the presentdocumentation for further information on the settings.

The user should be familiar with the operation of Microsoft Windows2000 /2003 Server and the database system used (Microsoft SQLServer or Oracle). The description of the configuration of a Server forinstalling the windream Server services, the administration of users andgroups in the operating system or the installation of the Microsoft SQLServer and the Oracle database instance are not part of thisdocumentation. You can find information on these topics in thecorresponding documentations of Microsoft and Oracle.

The windream Server installation consists of the followingcomponents:

• windream main services (windream DMS Service, windream TCPService, windream Agent, windream Thumbnail Service, windreamEvent Service)

• windream Database (SQL Server Database or Oracle)• windream Fulltext Service

System requirements 1-3

• windream Database Fulltext Extension (SQL Server FulltextCatalogue or the InterMedia components by Oracle)

• System Libraries (update of system components)• Microsoft MDAC 2.5

The respective components can be installed independently on one ormore computers (application server), whereas the elements "windreamMain Services" and "windream Fulltext Service" have to be installed onthe same computer.

The components "windream Database" and "windream DatabaseFulltext Extension" have to be installed on the same computer as well.Then, the installation of Microsoft SQL Server 2000 / 2005 or Oracle8i (v. 8.1.7.3 or higher), Oracle 9i (v. 9.2.0.4 or higher) or Oracle 10i (v.10.1.0.4 or higher ) is required on this computer.

The "System Libraries" are always (if necessary) installed on the samecomputer on which the "windream Main Services" are installed.

Component "Microsoft MDAC 2.5" is enabled (if necessary) in the listof components and is installed by setup on the computer on which thewindream Main Services are to be installed.

All windream server installations and configurations have to beexecuted with local administrator rights by the user, as services areinstalled and local users and groups have to be set up.

Note: You must not install the windream Server and thewindream Client on the same computer.

System requirementsThe necessary system requirements are listed below.

Client – server system architectureThe following client-server system architectures are supported:

• windream Server is installed on a Primary Domain Controller(PDC). We do not recommend an installation on a PDC.

• windream Server is installed on a Windows 2000 or 2003 Serverwhich is logged in at the Domain.

• windream Server is installed on a standalone Server. The applicationserver is not a Primary Domain Controller, and a Primary DomainController is not available and configured for the network sector.

• No DHCP configuration of the Server. E.g., a fixed local IP-addressassigned by a team-software is allowed. Nevertheless, a message will

1-4 System requirements

be displayed that for at least one network card DHCP is configuredand that the windream Service will not start automatically any moredue to security reasons, after the local IP-address has changed. Inthis case, please consider the notes in chapter "IP-address Server haschanged" in "Important notes on the installation and configuration "(chapter 4).

• windream Server may not be installed on a Backup DomainController (BDC).

• The use of 100 Mbit network cards is required for the windreamClient Server architecture.

• No computer with NetBIOS name "windream" may exist in thenetwork neighborhood. Also, the windream Server must not benamed "windream".

You will find further notes in section "windream – Common userconfiguration", page 1-15.

Designator of the domainThe designator of the preset domain (<MYDOMAIN>) can be viewedwith the command Start>Programs>Administrative Tools (Common)>UserManager for Domains. The designator of the current domain is presentedin the title bar of the dialog box displayed.

The description of the setup of a Windows 2000 / 2003 Server asPrimary Domain Controller (PDC) and for the administration of usersand groups in the current version of the operating system is not part ofthis documentation. You can find information on these topics in thecorresponding Microsoft documentations.

System requirements of the windream servicesFor the installation of the windream Server services the followingrequirements have to be fulfilled:

• Microsoft Windows 2000 Server with service pack 4 or MicrosoftWindows 2003 Server with service pack 1 must have been installed.

• Microsoft Internet Explorer 5.01 or higher with Active Desktop andTask Scheduler must have been installed.

• Microsoft MDAC 2.5 or higher must have been installed.• Microsoft Management Console 1.2 must have been installed.• For displaying and printing this documentation: Adobe Acrobat

Reader must have been installed.• windream ObjectStore (version 5.1 or higher) has to be installed.

This is only valid if the windream Archive shall be installed and if ithas been licensed (see section "Install the windream ObjectStore",pp. 1-10).


• For archiving index data of the windream objects and the objecttype information in XML-format: Microsoft XML 3(msxml3.dll Version 8.10.8303.0) must have been installed. Thisis only valid, if the ObjectStore service is installed and if thearchiving of windream objects shall be executed including XML-files (ObjectStore has been configured respectively).

Note: A later installation of the windream ObjectStore is alsopossible after an already executed windream Server installation anytime. However, if the ObjectStore (windream archive) shall beinstalled and used directly with the windream DMS, werecommend to consider the installation steps in the order they aredescribed. This will make some configuration steps obsolete, whichwould have to be made manually after a later installation of theObjectStore. The configuration steps are described in theinstallation guide of the ObjectStore service and in the windreamuser guide / online help.

The description of the ObjectStore Service and of the installation isnot part of this documentation. You can find a detailed descriptionof the ObjectStore Service and of the installation of the windreamObjectStore Service in the documentations referring to thewindream Archive System and ObjectStore Service.

How to check whether requirements are fulfilledVersion ofMicrosoft WindowsServer

1. Click Run in the Windows Start menu. 2. Enter winver into the input field. 3. Click OK.

The information (e.g. version) on the installed operating system ispresented in the dialog box displayed.

windreamObjectStore

In order to check if the installation of the windream ObjectStore hasbeen successful, open dialog box Services of the Control Panel viacommand Start>Programs>Administrative Tools>Services. The windreamObjectStore-Service will be displayed in the list of the servicesas started and indicating the Automatic startup type.

Microsoft InternetExplorer 5.01 orhigher with TaskScheduler

You can read from the number of the product version what version ofthe Internet Explorer is currently installed. Check whether the folderScheduled Tasks exists as folder in Settings>Control Panel. The schedulerwill be installed, if during the setup program of the Internet Explorerthe component for extended Internet Browser options is selected.


System requirements of the windream databaseFor the installation of the windream Database the followingrequirements have to be fulfilled (depending on the database systemused):

Microsoft SQL Server

• Microsoft SQL Server 2000 incl. service pack 4 or Microsoft SQLServer 2005 (9.00.1399) has to be installed. (When installing theSQL Server you have to take care, among other things, that thecodepage is set on the recommended value 1252 (ANSI-Server), thatthe fulltext search is installed and that the option of considering thecase sensitive sorting criterion is deactivated, see note.) Additionally,option SQL Server and Windows must be enabled.

We do NOT recommend to switch on the option of case sensitivity assorting criterium in SQL Server. This option should only be enabled, ifa case sensitivity is desired explicitly at the windream workstationswhen searching for index values. Please read the following note.

Note: If the option of considering case sensitivity as a sortingcriterium is NOT enabled, windream search operations will notconsider case-sensitivity. However, it is an advantage that existingSQL indices are used in this case. At the windream clients, thesearch option of case sensitivity must nevertheless be enabled sothat the system will not execute search operations using theUPPER() database function, which might result in a loss ofperformance.

• Microsoft SQL Server has to be started.

Note: If performance problems or problems with otherapplications occur when SQL Server is operating, the reason maybe the dynamic memory administration of SQL Server.

Dynamic memory administration of SQL ServerAs default, MS SQL Server administers its required memory (RAM)dynamically. When operating, SQL Server occupies requiredmemory for the processes to be excuted. Step by step, the dynamicmemory administration occupies more and more space withoutreleasing memory again for other applications. This will lead to aperformance reduction after a certain period of time.Additionally, problems may occur when other applications areoperating, too, if these are executed on the same computer and ifnot enough memory is available for them.In these cases, we recommend to restrict the memory size of SQL


Server. Depending on the individual requirements (number andtype of other applications), you will have to configure the size ofthe maximum RAM to be used by SQL Server. The database –meaning SQL Server - should then be assigned the maximumcapacity of memory available.The memory configuration – meaning the function for using apredefined memory size – can be executed over the memoryadministration of MS SQL Server Enterprise Manager.Additionally, we recommend to regularly terminate SQL Server andto restart it. This will ensure that memory which is not needed anymore will be released again.You will find additional information in the respective Microsoftdocumentation on SQL Server.

Size of transaction logfileDuring the operation, the storage capacity of the transaction logfilewill increase steadily. In order to prevent problems with hard diskcapacity, the transaction logfile should regularly be cut (meaningshortened) using the respective functions of MS SQL ServerEnterprise Manager. The following steps are then to be executed:

1. Shorten the database over a maintenance job.2. Execute a database backup after that.3. Shorten the transaction logfile.

Please cf. further information in the respective Microsoftdocumentation concerning SQL Server.

Oracle 8.i / 9.i / 10i (Standard / Enterprise Edition)

• Database Oracle 8i version 8.1.7.3 or higher, Oracle 9i version9.2.0.4 or higher or Oracle 10i version 10.1.0.4 or higher must beinstalled.

• InterMedia text option must be installed.• Oracle Client 8.1.7 with ORAOLEDB provider 8.1.7.3.2, Oracle

Client 9.2.0.4 with ORAOLEDB provider 9.2.0.5 or ORAOLEDBprovider 10.1.x must be installed.

Note: ORAOLEDB provider 10.2.0.1 may NOT be used, as –partly – a connection between the windream DMS server to thedatabase cannot be established. Further notes on this can be foundin the respective Oracle documentations.

• Database instance and service must be installed and started.• Access to the database instance over sqlplus via Net8 must be

possible.


How to check whether requirements of SQL Server arefulfilled

Microsoft SQLServer 2000

1. Click Programs>Microsoft SQL Server>Enterprise Manager of theWindows Start menu.

2. Switch to folder Console Root>Microsoft SQL Server>SQL Server-Group><windream DB-Server>.

3. Open dialog box SQL Server Properties (Configure) with the Propertiescommand of the context menu.

The information (e.g. version and codepage) of the installed SQLServer is displayed on tab page General.

Figure 1-1: SQL Server Properties

On the Security tab page, the option SQL Server and Windows must beenabled for authentication.

Microsoft SQLServer is started

You can read from the SQL Server Service Manager, whether the SQLServer is started (command Start>Programs>Microsoft SQL Server>ServiceManager).


Figure 1-2: SQL Server Service Manager

How to configure memory for SQL Server

1. Enable command Programs>Microsoft SQL Server>Enterprise Managerfrom the Windows Start menu.

2. Switch to folder Console Root>Microsoft SQL Server>SQL ServerGroup>windream DB-Server.

3. Open the dialog box SQL Server Properties (Configure) using theProperties command of the context menu.

4. Switch to the tab page for administering memory. 5. Enable the option for using a predefined memory size and

configure the size for the maximim memory to be used by movingthe indicator.

How to check whether the requirements of the Oracledatabase are fulfilledExecute a login at the desired Oracle instance using sqlplus. If the loginis successful, the Oracle database has been installed correctly and therequirements of the windream server installation are fulfilled.

System requirements hard disk driveEnsure that enough hard disk capacity will be available for thewindream database (SQL Server database, SQL Server fulltext files orOracle database). According to the expected amount of documents,you will additionally need capacity for:

1. The windream file storage (at least 1 GByte recommended) 2. The windream temporary directory (in addition to 1.: at least 500MB).

1-10 Installing the windream ObjectStore

Installing the windream ObjectStoreIf the archiving functions of the windream Archive (windreamObjectStore) are desired and if they have been licensed, the installationof the windream ObjectStore service should have been executed beforethe installation of the windream services. Documents which can beprocessed will be stored in the windream file storage, which existsindependently of the windream ObjectStore (see topic "windreamdirectories for file storage", page 1-31). In order to archive documents,the windream ObjectStore service must be installed (the service andthe program directory named "Objectstore" will be installed).

The description of the installation of the ObjectStore is not a part ofthis documentation. You can find a detailed description of theObjectStore Service and of the installation of the windreamObjectStore Service in the documentations referring to the windreamArchive System and ObjectStore Service.

Access permission for the windream mainuserDuring the windream Server setup the windream mainuser isautomatically entitled to access the windream ObjectStore Service. Butthis is only possible if the ObjectStore Service is installed on the sameapplication server as the windream Services (the windream Server).

Note: If the windream ObjectStore Service is not installed on thecurrent server, but on another one, that means that the windreamServer and the windream ObjectStore Service do not run on thesame server, or, if the ObjectStore is installed after the windreamServer services have been installed, the access right for thewindream mainuser has to be entered manually after theinstallation.For this, you execute the authorization withmmpasswd -add <mainuser> <passwd>in the directory windream objectstore\bin in an MS-DOS window. You receive information on the syntax of thecommand mmpasswd by entering mmpasswd –help.

Further requirements 1-11

Further requirementsBefore installing the windream Server services, the required windreamgroups and user accounts have to be created corresponding to theexisting client-server systems architecture. Ensure that an SQL ServerAdmin-Login or an Oracle DBS login for the installation of thewindream Database and the windream Database fulltext extensionexists. Before starting the windream Server setup program, you have toexecute the following steps:

• Create a windream group of all windream users.• Configure the windream user accounts.• Determine MS SQL Server authentication (when using SQL Server).• DBA login for Oracle authentication must be known or determined

(when using Oracle).

Note: Setup offers a separate dialog box for the configurationand logging of the windream group of all windream users and themainuser. The windream mainuser and the group are created andconfigured by the setup program according to the entries which aremade at this point. The mainuser as well as the group are onlycreated if they have not been available so far.Additionally, these entries are also used for the respective setting ofthe DCOM configuration of the DMS Service and the windreamServer services (DMS Service, Full-text Service, Thumbnail Serviceand Agent) in the system settings.For determining the SQL Server authentication while running thesetup program, an MS SQL Server administrator login is requiredwhich has to be created before starting the installation (only ifnecessary).For determining the Oracle authentication during the setup, anOracle DBA login is required which has to be created beforestarting the installation (only if necessary).

1-12 Creating windream group accounts

Creating windream group accountsThe user and group administration of windream is based on the userand group concept of Windows. The operating system users and groupaccounts and the group memberships of the users are determined inthe user administration of Windows.

Users and user groups must be configured as operating system users orgroup accounts and must be classified as windream users or groups forenabling a user to work with windream. The classification of the usersand groups and their administration is executed with the windreamManagement Console (WMC).

User groups whose members shall get access to windream are takenover into the windream database over the WMC as windream groups.

Changes of accounts or group memberships can only be executed overthe operating system user and group administration. A refresh(adjustment) of user and group accounts will then be executed in theWMC (function Add to windream and Adjust).

In the windream Business Edition, it is possible to create andadminister windream groups independent of the operating systemsusing so called internal windream groups. Except the windream groupof all windream users, all other groups can be created as internalwindream groups. However, respective operating system accountsmust always exist for the windream users and for the group of allwindream users. These must be applied to the windream user andgroup administration and must thus be classified as windream usersand groups.

A detailed description of the user and group administration ofwindream can be found under topic "User and group administration"in the windream administration guide.

Note: Setup automatically creates the windream group of allwindream users according to the entries determined during theinstallation, if these have not been available yet.Additionally, the windream group will be taken over into the userand group administration of windream.The configurations described below for creating the windreamgroups must only be executed manually, if you want to change theconfiguration after having completed the installation.

Two pre-defined windream groups are needed for the operation ofwindream:

• windream Users• windream Administrators

Creating windream group accounts 1-13

We recommend to create all windream groups under one designatorwhich begins with the expression named "windream" (for example"windream Users" or "windream Administrators").

windream users A windream group must exist to which all users are assigned who shallwork with windream. When running the setup program, this group willbe created as local operating system group on the windream Server oras global group on the PDC (if available); (default: windream-Users). Another option is to select a group which is already availableand to determine it as group of all windream users. The group of allwindream users configured in the setup program is taken over into theuser and group administration of windream. Users who are notassinged to this group cannot work with windream, which isindependent of the question in which groups they are members.

After having completed the setup routine, all users who shall work withwindream must be assigned to this group over the user administrationof the operating system. After that, the adjustment of this group mustbe executed in the WMC in order to refresh the changed groupassignments in windream, too (see topic "User and groupadministration" in the windream administration guide).

We recommend to create a new operating system group named"windream users" and to assign the desired groups and user accountsafterwards.

windreamadministrators

Further on, a windream group has to be determined for administrativetasks, for example a local operating system group named "windreamAdministrators". All users are to be assigned to this group who shallexecute management tasks in windream (access to functions providedby the windream Management Console (WMC)).

Thus, an operating system group is taken over into the windream userand group administration, which will be classified as windreamAdministrator Group there. You can also determine a windream groupwhich already exists as windream Administrator Group. These settingshave to be made after having completed the setup routine under theaccount of the windream mainuser. As long as there is no groupexisting which has been determined as Administrator group, only thisuser will have windream administration rights (see also topic "User andgroup administration" in the windream administration guide.

Only users of this classified group can execute management functionswith the WMC (windream Management Console).

1-14 Configuring windream user accounts

Configuring windream user accountsAfter the required windream group accounts have been created, thewindream user accounts have to be created with the functions of theuser and group administration of the operating system on thewindream Server. First, at least one windream mainuser account has tobe created (command User>New User). You can choose any designatorfor this user. For a simple identification, it is recommended to use"windream" as designator.

Note: Setup will automatically create the windream mainuser andthe windream group of all windream users according to the entriesmade during the installation, if these have not been available so far.

The creation of the windream mainuser account on the domaincontroller is not executed automatically by the setup program, incase that the windream Server is installed on a Windows2000/2003 Server, and the NT Server is logged-in at the domain. Inthis case, you will have to create the windream mainuser account atthe domain before installing the windream Server services. Whenoperating Trusted Domains, the windream mainuser has to becreated on all Domain Controllers (not executed automatically bysetup; see chapter "Creating the windream mainuser account").

The configuration of the windream mainuser – which is describedbelow – will only have to be executed manually if you want to makechanges after having finished the installation. Please also cf. notesreferring to the creation of common user accounts.

Creating the windream mainuser accountA windream mainuser account has to be created on the windreamServer as operating system user. The designator can be chosen as youwant. We recommend to use "windream", as this designator is simpleto use (for example: windream, complete name: windream mainuser,description: windream mainuser).

The name and the password of this user have to be entered in thewindream Server setup.

Please note that the following rights are to be assigned to thewindream maninuser after the installation:

• logon as service;• logon as batch processing job;• right to act as part of the operating system.

Configuring windream user accounts 1-15

See also topic "Operating system rights for the windream mainuser inchapter 2".

Additionally, the windream mainuser must be assigned to the localadministrator group of the operating system. This assignment is donein order to guarantee the correct system service processing (especiallystarting and closing the windream Agent).

Besides, the windream DMS Service, the Agent, the ThumbnailService, the Event Service, and – if desired - the windream FulltextService are executed in the context of this user. This determination ofthe user identification under which the services are executed is carriedout in the DCOM configuration and in Administrative Tools>Services forthe windream DMS Service and for the Thumbnail Service. For thewindream Fulltext Service and the Agent, it is carried out inAdministrative Tools>Services (see also chapter 2 "Configurationwindream Server Basic Settings").

With this name and password, the authorization of the windreammainuser for the windream ObjectStore Service is implicitly executed(see chapter "Installing the windream ObjectStore").

In case the Application Server is no Primary Domain Controller, but aPrimary Domain Controller is available and has been configured for thenet segment (for example <MYDOMAIN>), the windream mainuseraccount must additionally be created on the respective Domaincontroller with the same name and password. This user must then beselectable for example under <MYDOMAIN>\windream in the userlists of the Application Server.

When using Trusted Domains, the windream mainuser has to becreated on all Domain Controllers.

The mainuser has windream administration rights, meaning he canexecute admin functions with the WMC over this user account. Afterhaving installed windream, the windream Administrator Group will bedetermined under the account of this user.

Note: In order to avoid incorrect entries, the respective dropdownlists and the available entry support for user and group lists shouldbe used in the group and user administration of the operatingsystem.

windream - common user account configurationDepending on the existing system architecture, you have to follow thedifferent approaches of the user authorization during the windreamuser configuration.


windream Server isinstalled on PDC

All connected windream workstations must log in to the domain,which administers the rights of the windream Server. All connectedWin9x workstations must obtain their user lists and group lists fromthe domain which administers the rights for the windream Server (seealso section"Creating windream group accounts", pp. 1-12).

windream Server isinstalled onWindows 2000 /2003 Server and thisserver is logged onto the domain

A local creation of windream user accounts (except of the windreammainuser) is not necessary. In addition, the members of the globalgroups, which are assigned to these local windream groups, are alsotaken into account.

All connected windream workstations have to log in at the domainwhich administers the rights for the windream Server (tab page fornetwork identification or computer name in the workstationproperties).

Figure 1-3: Identification of the connected Windows 2000 workstations

windream Serverinstalled onStandalone Server

The windream user accounts have to be created locally.

On client (workstation) and server, users have to be identical (use thesame name and password).

All users of NT workstations must log in to their workstations locally

Configuring windream user accounts 1-17

(network identification on the properties tab page of the workstation).

Figure 1-4: Identification of the connected Windows 2000 workstations (standalone server)

Here, you have to take care that a workgroup and not a domain isadjusted. Changes and identifications can be executed over thecommand button Properties on the tab page Network Identification (e.g.adjust the option Workgroup).


Figure 1-5: Identification change of the connected Windows 2000 workstations (standaloneserver)

MS SQL Server authentication 1-19

MS SQL Server authenticationsetup will execute the configuration of the windream database tableswith the user account for the windream mainuser. Additionally, thewindream DMS Service will log in to the windream database via theuser account of the windream mainuser. Thus, the option SQL Serverand Windows must be enabled in SQL Server Enterprise Manager for thewindream database (tab page Security of SQL Server Properties (configure)<windream DB Server> in MS SQL Server Enterprise Manager).

How to check the adjustment of the authentication in SQLServer Enterprise Manager

1. Switch to the folder Console Root>Microsoft SQL Server>SQL Server-Group><windream DB-Server>.

2. Open the dialog box SQL Server Properties (Configure) with commandProperties in the context menu.

3. Switch to tab page Security. 4. Click option SQL Server and Windows in group Security. 5. Close the dialog box by clicking OK.

Figure 1-6: SQL Server properties – security

1-20 MS SQL Server authentication

Possible authentication modesThe creation of the windream mainuser account and the windreamdatabase in SQL Server can be executed by the setup program via twodifferent authentication modes.

During the windream Server setup, an SQL Server login will berequired for the installation of the windream database and the fulltextextension of the windream database. Before starting the windreamServer setup program, you will have to ensure that an MS SQL Serveradministrator login is available.

Thus, you have to select one of the following options:

• Windows NT authentication• SQL Server authentication.

Depending on the desired type of authentication, the respective settingshave to be executed in SQL Server Enterprise Manager before startingthe setup of the windream Server (command Start>Programs>MicrosoftSQL Server>Enterprise Manager).

Windows NTauthentication shallbe used

If the local logged-in Windows user is in the SQL Server administratorgroup, the option Windows NT Authentication can be chosen in the SQLAuthentication dialog of the windream Server setup. Then, an entry ofname and password in the windream Server setup is not necessary.

SQL Serverauthentication shallbe used

In this case, you have to select the option SQL Server-authentication in thewindream Server setup. When you enter names and passwords youhave to indicate an explicit user (e.g. "sa") existing in the SQL ServerEnterprise Manager under Console Root>MS SQL Server>SQL ServerGroup><windream DB-Server>>Security>Logins.

Figure 1-7: SQL Server Authentication

If the user "sa" does not exist, a new user account, e.g. "administrator"with the Server role has to be created (Console Root>MS SQLServer>SQL Server Group><windream DB-Server>>Security>Logins).

Oracle authentication 1-21

Figure 1-8: SQL Server login properties – new user

Do NOT use the windream mainuser in the windream Server setup(this user will be created during the windream setup).

A login as user of a Windows administrator group (e.g."administrator”) does not likewise work, as long as this user"administrator” is not explicitly configured in the SQL ServerEnterprise Manager with the Server role as system administrator.The only existence of the Windows group "BUILTIN\Administrators"in the SQL Server Enterprise Manger is not sufficient.

Oracle authenticationDuring the setup of the windream Server, an Oracle DBA login willbecome necessary for installing the windream database and the fulltextextension. Thus, ensure - before starting the setup - that an Oracledatabase administrator login is available. In the dialog box for enteringthe authentication, the explicit authentication will be enabled. An NTauthentication is not available with Oracle. Thus, the respective optioncannot be chosen.

For an explicit authentication, the name and the password of an OracleDB administrator have to be entered in the setup. This DBA must be

1-22 Installing the windream server (starting the setup program)

equipped with the right to create user accounts and databases on thedesired Oracle instance.

Note: The default setting after an Oracle installation is:user:system / password:manager (DBA Name: system / password:manager). The data used for the windream mainuser should notbe used for the Oracle authentication.

Installing the windream server (starting the setup program)After having considered all aspects mentioned so far, you now launchthe windream Server setup from the installation CD (setup.exe)inorder to install the windream Server.

Language versionwindream supports several languages. According to the requirements,you receive the respective installation CDs in the desired languageversion. The language of the current setup determines which defaultcolumn designators are entered in the windream database and in whichlanguage the windream dialogs appear. The column designators can bechanged later over the windream Management Console.

The language in which the windream dialogs are presented can bechanged over a manual change in the Windows Registry. We do notrecommend this manual change.

Open the Registry and choose pathHKEY_LOCAL_MACHINE\Software\windreamGmbH\windream\<windream version>\NLS. Change thelanguage by entering the respective number for the Language.

English Language = 001

German Language = 049

Then, you change the local ID Mapping (entry LCIDMapping). Theexisting language of the operating system will be mapped according tothe windream Setting.

English LCIDMapping= 001#7/1/0,001#9/1/0

German Language = 049#7/1/0,049#9/1/0

Installing the windream server (starting the setup program) 1-23

Starting the setup programStart the setup program from the CD and follow the instructions.

Software licence agreementPlease read the Software licence contract carefully. With the installationof the windream Server you accept the licence agreement.

Information on system requirementsHere, the necessary requirements of the system are listed again.

Type of setupAfter that, you select the type of the setup to be executed in the dialogbox setup Type. You can execute a user-defined installation or thestandard installation.

Figure 1-9: Choose Type of setup

• Standard• User-defined

During the standard installation, the most important components areinstalled. A later adjustment, that means a following installation ofsingle components is possible over the setup at any time. If you choosethe user-defined setup, you can make a selection of those componentsyou like to install.


Selecting components (user-defined only)Here is a selection of the below listed components of the setup:

Regarding the installation of components, please read the indications inthe section "Basics of the windream Server Installation" pp. 1-2.

• windream Main Services• windream Database• windream Fulltext Service• windream Database Fulltext Extension• Microsoft ADO 2.5

Figure 1-10: Select Components

If a previous installation has failed, a post-installation can be executedhere over the selection of the respective components. A post-installation of the windream Database and of the windream DatabaseFulltext Extension is recommended, if the installation has failedbecause of e.g. the wrong entry of the MS SQL Administrator Login orOracle DBA Login.

windream mainservices

An installation of the windream Main Services (windream DMS-Service, windream TCP Service, Agent and Thumbnail Service)follows.

Additionally, the windream Management Console (WMC) is installed,and the windream program folder is created..

During the registration of the windream Agent, an entry will be created


in the Scheduled Tasks folder which is required for archiving and deletingobjects (process archive and delete objects).

MS SQL Server:

windream database The windream Database is created on the SQL Server, which is to beselected, and it is filled with initial values.

Oracle:

The windream database will be created on the Oracle instance whichcorresponds to the Oracle Net8 service name to be determined in thesetup.

Here, you have to take care that the selection of the language alsodetermines the initial description of the default column designators inthe windream database in the respective language (see also section"Language Version of the setup", pp.1-22.

windream fulltextservice

The windream Fulltext Service is installed.

windream databasefulltext extension

MS SQL Server:

The Fulltext catalog necessary for the fulltext search is created on theSQL Server, which is to be determined.

Oracle:

The InterMedia components necessary for the fulltext search arecreated on the Oracle instance specified by the Net8 service name.

Refresh systemlibraries

The setup program checks existing system libraries and installs missingor newer versions of the necessary components (DLL files) ifnecessary.

Note: The selection of the component System Librariescannot be deactivated manually, if the windream Main Servicesshall be installed (component windream Main Services isactivated).

windream database typeHere, you determine the database type, if you only want to install thewindream Server components without database components.


Figure 1-11: Selecting the database type

Updating system librariesIn case the setup should discover that system libraries are missing orthat existing components are not updated, these will be displayed in adialog box and installed again.

When updating the system libraries, an installation of the remainingwindream Services is not executed with it. Afterwards, for theinstallation of the windream Services, the server has to be started againand the setup has to be called up again (see the indications in the setupdialog boxes).

Installing the databaseHere, you determine whether the setup program shall install or updatethe windream database automatically, or whether it shall only run theinstallation routines with the procedures for manual installation /adjustment of the database.


Figure 12: Installation of the windream server – installing the windream database

Install database Use this option, if the required actions for a (new )installation or for anupdate of the windream database shall be run by the setup program.This is the default setting.

Only log databaseevents

Use this option, if the required events shall not be run by the setupprogram, but manually. The setup program will then create the requireddirectories in the windream program folder (\windream\DB\),install the required files and log the steps to be made manually in fileDB\Database_Actions_<timestamps>.log.

windream user authenticationThe user and group administration of windream version 4.0 supportsWinNT and LDAP (Lightweight Directory Access Protocol) as ActiveDirectory service providers. Depending on the provider used, youselect the respective option here.


Figure 13: Installation of the windream server - windream authentication

Active DirectoryWinNT provider

Use this option, if the functions of the WinNT provider shall be usedfor the windream user and group administration. This is the defaultsetting.

In this case, local users and groups of the windream server and alsousers and groups of the Active Directory domain can be used.

You can only use one group hierarchy level. This means that a global oruniversal group can be member of a local windream group. No furthergroup hierarchies will be evaluated.

Active DirectoryLDAP provider

Select this option to use the functions of the LDAP provider. In thiscase, you will only be able to use user and group accounts of the ActiveDirectory domain. This also refers to the windream mainuser and tothe group of all Wd users.

Several group hierarchy levels can be used. This means that a global oruniversal group can be member of a local windream group. Furthergroup hierarchies will also be evaluated; this will also allow complexgroup hierarchies.

LicensingIn the dialog box windream Licensing you indicate your name, company,department and the licence key, which you received from yourwindream partner.

The licence key contains the respective licences applied for, the periodsof validity and installation properties (for example 'test') in encryptedform.


Figure 1-14: Licence information

You can read in (copy and paste) the license data which you receivedfrom your windream partner over the command button From file(standard file name: WMCustom.ini) to avoid mistakes which mightoccur if the key is entered manually.

Select destination folderIn the dialog box for selecting the destination folder, you enter thedestination folder for the windream Server installation.

windream TDI-settingsHere, you enter the port number in the field Port, over which theconnected windream workstations will communicate with thewindream server. The port number is preset (default 534), but it can bechanged.

This port number is entered in the file\system32\drivers\etc\Services on the windreamServer. This port number has to be determined during all windreamsetups at the workstations.

Note: Ensure that the port number entered is not occupied byanother service. Port 534 which is pre-occupied by the setupprogram is reserved for windream and shouls thus not be occupiedby other services. Earlier versions of windream used port 1122.This port number will not be changed by windream updateinstallations on the Server.


Figure 1-15: TDI-Settings

If the port number is used by other services nevertheless, thewindream TCP Service cannot be started again (error in file mm-tcp.log WSAADDRINUSE). In this case, the port number in Servicefile (\system32\drivers\etc\Services on the windreamServer ) must be changed (for example to 534). After a restart of thewindream TCP Service, the TDI settings on the workstations must beadjusted respectively (in the windream configuration on tab pageDriver).

windream ObjectStore presettingsIn the dialog box windream ObjectStore Settings you enter the server nameand the port on which the windream ObjectStore service is installed(see section "Install the windream ObjectStore", pp. 1-10). If theObjectStore is not to be installed, you can leave out this entry, or youenter the data of an installation planned for the future. Entries madehere are presettings for the dialog boxes in which the windreamstorages are configured in the windream Management Console.

Additionally, the windream mainuser is authorized to access thedetermined ObjectStore here. This is only possible in case theObjectStore Service is installed on the same application server as thewindream services (meaning windream server).


Figure 1-16: Enter ObjectStore data

Server Here, you enter the name of the server on which the windreamObjectStore Service is installed. If the ObjectStore Service is installedon the local application server, the default setting will be correct.However, this name has to be checked. The local server name<LOCALSERVER> is preset.

If the ObjectStore is installed on another server and this one is not thecurrent server, you will have to enter the name of this server (seesection "Install the windream ObjectStore", pp. 1-10).

If the windream ObjectStore Service is not installed, you can leave outthis entry, or you enter the data of an installation planned for thefuture.

Port In this field, the port configured for the windream ObjectStore servicehas to be entered (see section "Install the windream ObjectStore", pp.1-10). Port number 6011 is preset.

If the windream ObjectStore Service is not installed, you can leave outthis entry, or you enter the data of an installation planned for thefuture.

windream directories for file storagewindream administers its documents in storages which are to beconfigured for this purpose. There are two different storage areas forthe administration of documents, one for documents which can beedited and one for those which are archived:

• windream file storage


• windream ObjectStore (if the windream Archive has been licensed).

When configuring the document types in the WMC, the settings of thedocuments' life-cycle are determined. Then, a working area is set fordocuments which can be edited. For the archiving period, documentsare administered in a specific archive storage.

The working area is always linked with a windream storage of a "filestorage" type. The archive area can either be linked with a windreamstorage related to a file storage or related to an ObjectStore. In order toarchive objects in an ObjectStore, the archive area must be related to awindream ObjectStore. The windream ObjectStore Service must beinstalled, and the respective windream ObjectStores must beconfigured.

The configuration of the windream storages (file storages andObjectStores) is executed in the windream Management Console.

windreamfile storage

windream administers its documents which can be edited in storages ofthe "file storage" type, which are to be configured and which are relatedto directories of the windream Server. These file storages areindependent from any windream ObjectStores.

The working area of a document type is configured as a windream filestorage area. windream will store the respective document in theassigned windream file storage.

New documents are first assigned to the standard object type(Standard). Thus, windream will save these documents in the filestorage assigned to this type. The directory for the file storage isconfigured in the setup.

Further on, the windream temporary directory can be configured.

windreamObjectStore

windream administers archived documents in the ObjectStore. AnObjectStore is related to a pool of the windream Archive. The possiblepools are configured with the installation of the windream ObjectStoreService (windream Archive). The archive area of a document isconfigured with a windream ObjectStore, if the archiving is executedover a windream Archive. Otherwise, the archive area of a document isconfigured with a respective windream file storage.

If archiving functions shall be executed with the windream Archive,the ObjectStore Service must be licensed and installed.

windream file storage directory (work sector of thestandard document type)In the dialog box windream FileStore Directory, you determine thedirectory in which documents are stored with the standard object type.


Determine a directory here which is equipped with sufficient capacityfor saving new incoming documents.

Figure 1-17: Configuration of file storage directory

The working area of the Standard object type is configured on thiswindream file storage. The configuration can be post-modified in thewindream Management Console.

All new documents are firstly assigned to the standard type bywindream. After that, documents can be assigned to another type,whose working area may refer to another windream file storage.

The minimum size of this directory can be read from the systemrequirements. The directory of the windream file storage may not bethe same as that which has been determined for the windreamtemporary directory.

Note: This directory (as well as later configurable directories forthe filing of files) should be created on a NTFS file system(configurated with a small block size, e.g. 1024 byte) in order not towaste any hard disk space.

For this file storage (default name WORK), a respective entry is createdin the windream storage table named ObjectStore, whichcontains the reference on the determined directory. The configured filestorages and the ObjectStores are administered in this table. For eachfile storage and for each ObjectStore, there is one entry with therespective references on the storage locations (directories or servernames and port numbers).


windream temporary directoryIn the dialog box windream Temporary Directory, you determine thedirectory in which temporary files are to be stored by windream. Thedirectory <windream Program Directory>\Temp is presetas default.

Figure 1-18: Determination temporary directory

Please ensure that enough capacity is available in this directory forstoring files:

• Files to be read regularly from the connected windreamObjectStores. The number of these files can be set in the windreamObjectStores (option binary files in the Cache area on the tab pageCommon) and is valid for each single windream ObjectStore. Thenumber of configured windream ObjectStores can be read from theWMC, or from the table named ObjectStore over the columnszAlias. For each single windream ObjectStore, there is an entryin the WMC (folder All windream Stores) or in theObjectStore table.

• Temporarily created copies of documents for which the full-textshall be extracted.

• Logfiles created by the windream TCP Service and the windreamFull-text Service.

The windream temporary directory may not be the same like thatwhich was configured as the windream file storage during the setup.

The minimum size of this windream temporary directory can be readfrom the system requirements.


windream databaseIn the dialog box windream Database you enter the database data.Depending on the database used (SQL Server or Oracle), one of thefollowing dialog boxes will be displayed. Entries are the same in bothboxes, except the SQL DB server name and the Oracle Net8 servicename.

MS SQL Server

Figure 1-19: Entering database information for SQL Server


Oracle

Figure 1-20: Entering database information for Oracle

DB server name orNet8 service name

In the field DB Server Name, you enter the name of the server onwhich Microsoft SQL Server is installed. The local server name<LOCALSERVER> is preset.

Oracle Database:

In the field Net8 Service Name, you enter the name of the Oracle Net8Service over which the Oracle instance for the windream database willbe addressed.

If you do not know the service name, you can either trace it over fileListener.ora or using the Oracle Net8Assistant / NetManager.

From the file Listener.ora,entry SID_NAME (here for exampleoracle8service):

Excerpt from file Listener.ora:

SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = D:\Oracle\Ora81) (PROGRAM = extproc) ) (SID_DESC = (GLOBAL_DBNAME = oracle8service) (ORACLE_HOME = D:\Oracle\Ora81) (SID_NAME = ora8hob)


) )

Using Oracle Net8Assistant / NetManager:

1. Start Oracle Net8Assistant / NetManager. 2. In Net8Assistant, switch to folder Net8-configuration>Local>Servicenaming.

3. Select entry <SERVICE>.<DOMAIN>.

The name of the Oracle service will be displayed in field Service name ofthe group Service Identification.

DB name Here, you enter the name of the windream database.

As default, the name is preset by windream.

DB ID Unique database ID. During test installations, it can be indicated with1. Otherwise, indicate the DB-ID which you received from yourwindream partner.

Note: If the licensing data are read from the file which youreceived from your partner, the DB-ID will also be read and presethere (see chapter "Licensing Data", page 1-28).

DB mainuser/password /passwordconfirmation

In the fields DB mainuser, password and Confirm password you enter thename and the password of the created windream mainuser (see alsosection "Configure windream Users", page 1-14) .

If the user account has not been created yet, the setup program will doit (except that the account of the windream mainuser has been createdon a domain and the windream Server is NOT the domain controller).If the user account is received from a domain controller, you enter thename as follows: <DOMAIN>\Username.

Note: In case the windream mainuser determined here shouldalready have been configured on the target system, the passworddetermined here will be checked. Messages will be displayed, if thischeck fails, if the determined user-ID does not exist or if thepassword is incorrect. The setup program will not be cancelled.You will be able to correct your entries before the setup programcontinues. In any case, assure that the user-ID or the password arecorrect.


Path for SQL Server OSQL programThe database installation in SQL Server is executed over the serviceprogram osql.exe (the respective calls are logged in the fileWMInst.log after the execution of the setup). In case that setupshould not find in the expected program directory of the SQL Server, adialog box will be displayed in which the complete path referring to thisprogram can be entered. Generally, this case does not occur, and thedialog box will only be displayed, if this specific case occurs.

Path for Oracle sqlplus programThe Oracle database installation is executed over the service programnamed sqlplus.exe (the respective calls will be logged in fileWMInst.log after having executed the setup). If setup should notfind this program in the expected Oracle program directory, a dialogbox will be displayed in which the complete path of this program canbe entered. Generally, this case should not occur, and the dialog boxwill only be displayed if this case occurs.

Oracle database settingsThis dialog box will only be displayed if windream is used with Oracle.Otherwise, you can proceed with topic "windream user / groupconfiguration". You will have to enter the tablespace designator, withwhich the windream mainuser shall be created on the Oracle instancewith the previously entered Net8 service name.

Figure 1-21: Installation of the windream-Server – Oracle Database Settings


User tablespace Here, you enter the name for the User Tablespace. As default, thename is preset with USERS.

Temp tablespace Here, you enter the name for the Temp Tablespace. As default, thisname is preset with TEMP.

Index tablespace Here, you enter the name for the Index Tablespace. As default, thevalue is preset with the name of the user.

The entries made here are used by setup to configure the windreammainuser for the Oracle Instance over the following command:

CREATE USER windream IDENTIFIED BY <password>DEFAULT TABLESPACE USERSTEMPORARY TABLESPACE TEMP QUOTA UNLIMITED ONUSERS

Additionally, the indices will be created in the defined index Tablespaceduring a new installation. When updating the system, only the newlyadded indices will be created in this tablespace. The tablespacesdetermined here must have been created bevor the installation of thewindream database.

Oracle CTXSYS loginEnter the user login for the Oracle CTXSYS user here. This dialog boxonly appears if windream is used with Oracle. Otherwise, you proceedwith chapter "windream User / Group Configuration". Please enterthe Oracle CTXSYS user name here (default: ctxsys) and thepassword. This login will be used for assigning the right of executingjobs for fulltext indexing (ctx_ddl) to the windream mainuser (seealso chapter "Oracle Jobs for Fulltext Indexing" in chapter 2).


Figure 1-22: windream-Oracle CTXSYS login

windream user / group configurationA separate dialog box is offered for the configuration and the creationof the windream mainuser account and the windream group of allwindream users by the setup. In this dialog box named windreamUser/Group configuration, you enter the information with which thewindream mainuser is created and configured by setup (for examplelogin name, identification and group name). In order to determine thewindream group of all windream users, you select one of the optionsoffered.


Figure 1-23: windream user / group configuration

windream mainuserIn this group, you enter the user identification (login name, full nameand password) of the windream mainuser, under which the setup shallcreate the windream mainuser account. In the Confirm field, you haveto enter the password once again.

The fields are preset with the default name for the login (windream)and the complete name (windream mainuser) of the windreammainuser to be created as account.

The mainuser account will only be created again, if he has not yet beenavailable so far. Additionally, these entries are used for the respectivesettings of the DCOM configuration of the DMS Service and thewindream Server services (DMS Service, Fulltext Service, Agent, EventService and Thumbnail Service) in the system settings.

The fields concerning the windream mainuser are disabled, if youalready made the required entries in the dialog box of the windreamdatabase.


Please note that the windream mainuser account has to be createdadditionally at the respective domain controller with the same nameand password, if the windream Server is installed on a Windows2000/2003 Server and if the Server is logged-in at the domain. This isnot executed automatically by setup. If Trusted Domains are used, thewindream mainuser is to be configured on all Domain Controllers (notexecuted automatically by setup).

In case the windream mainuser determined here should already havebeen configured on the target system, the password determined herewill be checked. Messages will be displayed, if this check fails, if thedetermined user-ID does not exist or if the password is incorrect. Thesetup program will not be cancelled. You will be able to correct yourentries before the setup program continues. In any case, assure that theuser-ID or the password are correct.

windream GroupsSelect the desired option here to determine the group of all windreamusers. An operating system group must exist, in which all users aremembers who shall work with windream. After the installation, thisgroup will be taken over into the windream user and groupadministration. Only members of this group will have access towindream. Thus, after having completed the installation, all users whoshall have access to windream must be assigned to this group in theuser and group administration of the operating system. After that, youadjust this group in the windream user and group administration overthe WMC in order to apply the changes in windream. A detaileddescription of the windream user and group administration can befound under the respective topic in the online help and the windreamadministration guide.

In order to determine the windream group of all users, you can create anew group or select an operating system group which is alreadyavailable.

• Create as local group (recommended)• Create as global group (not recommended)• Select existing group (not recommended)

Create as localgroup

Select this option to create a new operating system group on thewindream Server (recommended). Setup will create the new group withthe entries in fields for the group name and the comment. These fieldsare preset with the default values for the windream group (windreamUsers and All windream Users). The entries can be changed.However, we recommend to apply the presettings.

The group will only be created again, if it has not been available so far.

All users who shall have access to windream have to be assigned to this


group over the user and group administration of the operating systemafter having completed the setup routine.

Create as globalgroup

If the windream Server is installed on a PDC and if you want to createa new global operating system group, you will have to select thisoption. Setup will create this new group with the entries in the fieldsfor the group name and the comment. The fields are preset with thedefault values for the windream group (windream User and Allwindream Users). The entries can be changed. However, werecommend to apply the presettings.

The group will only be created if it has not been available so far.

All users who shall have access to windream have to be assigned to thisgroup over the user and group administration of the operating systemafter having completed the setup routine.

Note: The option for creating a global group will only be enabledif the windream Server is installed on a PDC.

Selectexisting group

Select this option, if you want to determine an already existingoperating system group as windream group. You determine the desiredgroup over the command button for selecting a group.

When entering the group name you should consider that the designatorof the Domain or the Server on which the selected group is createdmust also be determined (<MYDOMAIN>\Group name orServer name\Group name).

The following actions will be executed with the data entered:

• windream mainuser will be created if not available yet.• Group "windream Users" will be created depending from the option

selected (if not yet available) and taken over into the windream userand group administration.

• DCOM settings for the windream DMS Service and the ThumbnailService will be made.

• Settings for the windream Services (DMS Service, Fulltext Service,Agent, Event Service and Thumbnail Service) are made in thesystem settings.

Note: After a re-installation of windream during which thewindream group “windream user” is created, the installing user(e.g. “administrator”) will not be authorized to use the windreamservices on the Server. He will receive the error message0Χ80070005 (access denied) e.g. when selecting the tab pageFilter of the windream configuration or when opening thewindream Management Console.


In order to be able to use and administer the windream Services asinstalling user (for example "Administrator"), the user must bemember of at least the windream groups named windreamUser (the group of all windream users) and of the windreamAdministrator group.Thus, after having completed the installation, you will have toassign the users to the respective groups in the user and groupadministration of the operating system. After that, these groupsmust be taken over into the user and group administration ofwindream, the administrator group must be determined and theadjustment must be executed. These configurations are to beexecuted under the user ID of the windream mainuser (see alsotopics "Create windream Group Accounts", "Create windreamUsers" and "Further Requirements of the operation of windream“in chapter 1 and 2).

Select program folderIn the dialog box Select Program Folder you enter the program folder,under which the windream programs shall be displayed in the Startmenu.

SQL Server authenticationHere, you select the kind of authentication for the MS SQL Server forinstalling and configuring the windream database. In SQL ServerEnterprise Manager, the option SQL Server and Windows must be set forauthentication in the windream database Server (tab page Security of theSQL Server Properties Configuration - <windream DB Server> of MS SQLServer Enterprise Manager).

Please consider the notes described in the section "MS SQL ServerAuthentication".

If you use Oracle, proceed with topic "Oracle Authentication".


Figure 1-24: SQL Server authentication

Note: In order to check the user data entered, setup will try a loginto the previously determined database with the user ID entered. Incase of errors, respective messages will be displayed. In order tosolve errors, you can correct the entries in the dialog fields for theconfiguration of the database(windream Database and SQL ServerAuthentication). Setup can also be continued at this point withoutchanges. In this case you will recieve a message that the databaseinstallation cannot be executed correctly, as no login to the databaseis possible.

Windows NTauthentication

Choose this option, if the currently logged in user is a member of theSQL Server admin group and if the NT authentication shall be used asMS SQL admin login. Generally, the setting Windows NT authentication issufficient (default).

SQL Serverauthentication

Choose this option, if the SQL Server authentication shall be used asMS SQL Server Administrator Login. In the fields Name and Passwordyou enter the user identification of the user who has previously beenlogged in to the SQL Enterprise Manager (see also chapter "MS SQLServer Authentication", page 1-19).

Oracle authenticationAt this point, you enter the authentication data for installing andconfiguring the windream database.

Please also consider the notes described in chapter "OracleAuthentication".


Figure 1-25: Oracle authentication

Explicitauthentication

Oracle only supports the option of an explicit authentication. An NTauthentication is not available with Oracle. Enter the data of the OracleDBA login to be used in the fields for the DBA name and thepassword (see also chapter "Oracle Authentication").

Note: In order to check the user data entered, setup will try a loginto the previously determined database with the user ID entered. Incase of errors, respective messages will be displayed. In order tosolve errors, you can correct the entries in the dialog fields for theconfiguration of the database (windream Database and OracleAuthentication). Setup can also be continued at this point withoutchanges. In this case you will recieve a message that the databaseinstallation cannot be executed correctly, as no login to the databaseis possible.

Start copying processAfter that, you start the copying process from the respective dialog boxfor installing the windream Server.

Please ensure that the entries are set correctly. Especially the licencinginformation, the IP address and the port settings should be checkedcarefully.


Figure 1-26: Start Copying Process

Starting the windream servicesStart the windream Services by confirming the message.

Figure 1-27: Starting the windream services

Setup completeAfter having completed the installation, you can display the readme fileand the logfile. It is not necessary to reboot the computer.

1-48 During the installation

Figure 1-28: Setup complete

During the installationDuring the installation, six MS-DOS windows will be displayed forcreating the windream database, the database fulltext extension and theconfiguration of the windream fulltext service, which will be closedagain automatically after some seconds.

Installation Number of MS-DOS windowsInstallation windream database 3 windows

Installation windream databasefulltext extension

1 window

Installation windream fulltextservice

1 window

Table 1-1: Number of MS-DOS windows during installation

In case the display of these MS-DOS windows should be closed veryquickly, or the windows are not displayed, this might be a hint towardsan incomplete installation.

Please regard especially the notes in the chapter "Installation“, page 1-49 and the "windream tips and hints" (chapter 4).

Installation completewindream creates the WMShowLg.bat file in the windreamapplication directory, which contains all logfiles created by the setup.According to these files, you can check whether the installation has

Installation check 1-49

been executed successfully. These files can be displayed after theinstallation. Additionally, you can start the windream services and thewindream Control Center at the end of the installation by confirming arespective message.

Viewing logfilesAt the end of the installation, you can determine throughout a specificoption that all logfiles created by setup and the respective readme fileson the Server installation are displayed automatically.

You can also display these files afterwards by executing theWMShowLg.bat file from the windream program directory.

Starting the windream servicesAfter the installation has been completed successfully, the windreamservices can be started, and the type of start can be set toAutomatical. Further on, the windream Control Center islaunched, with which the windream Configuration and the windreamService Manager can be started.

Oracle job for fulltext indexingFor fulltext indexing, an Oracle job will be configured by the Serversetup. In order to execute this job, entryjob_queue_processes = 2 must be set in the Oracleinitializing file. This setting must be made manually after havingcompleted the setup routine under Oracle 8i. Setup will edit arespective message, in which the name of the initialzing file and thedirectory of the file has been placed is mentioned (see also chapter 2 onOracle jobs for fulltext indexing). Under Oracle 9i, this setting is madeby default and need not be adjusted.

Installation checkAfter a successful installation, some checks have to be executed. Theseare:

• Check whether windream Services have been started.• Check of the windream setup logfiles.

If parts of the installation should have failed, the respectivecomponents are to be installed once again (see also chapter 1).

Additionally, you will find information on errors in the "Tips andHints" chapter.

1-50 Installation check

Checking whether windream services have beenstartedDuring a new installation, the start type for the windream Services isconfigured as automatical in Programs>Administrative Tools>Services.Additionally, the services should definitely be started after theinstallation is complete and after having confirmed a respectivemessage. In Programs>Administrative Tools>Services or over the ServiceManager of the windream Control Center, you can check the start typeand whether the Services have been started. If some of the serviceshave not been started, you can look for hints in the respective logfilesor in the Server event log (command Start>Programs>AdministrativeTools>Event Log) (see also "List of windream Server Logfiles andDiagnostic Outputs", page 1-51 ff).

How to check whether the windream services have beenstarted

In theadministrationsettings

1. Switch to the Windiows administration with commandStart>Programs>Administrative Tools.

2. Open the dialog box Services.

The respective services with their status and startup are displayed in alist.

Or

From the windreamControl Center

1. Open the windream Control Center with a click of the right mousebutton on the windream icon in the task bar.

2. Enable the command Service Manager.

Checking the windream setup logIf errors should have occurred during the creation of the database/thedatabase user, during the initial filling of the database or during thecreation of the fulltext components, the created SQL logfiles can befound in directory windream/DB (<windream ProgramDirectory>\Db) (as an example, an incorrect MS SQL ServerAdministrator Login will be documented here).

In this case, the installation of the components windreamdatabase and/or windream database FulltextExtension has to be executed again (see also chapter “Installwindream Server (Launch setup)” page 1-22.).

If necessary, the windream database and the database user are to bedeleted. This can be executed with SQL Server Enterprise Manager orin Oracle DBA Studio / Enterprise Manager or via file dropDB.bat.


Note: In the directory <windream Programdirectory>\Db (respectively the Oracle directory), a filenamed dropDB.bat is created during the windream installation.The windream database, the created windream database user andthe windream jobs (SQL Server Agent jobs) or the windreamfulltext indexing jobs (only Oracle Enterprise Edition) can bedeleted when this file is launched.In order to avoid the deletion by mistake, the respective launchcommands have been disabled (command line beginning withrem). If the database (incl. SQL Server jobs and fulltext indexingjobs) and the user accounts shall be deleted, the respectivecommand lines have to be enabled again before the file is executed.The delete commands for deleting the database components aregenerated for the SQL Server or Oracle authentication, anddepends on the settings made during the setup (see chapter "MSSQL Server Authentication" or "Oracle Authentication", page 1-19ff). If the option SQL-Server Authentication has beenselected, the password determined there will not be entered in thebatchfile. For deleting the database components, the password musthave been entered before manually (substitute entry<SQLAdminPasswd> by the passowrd).In the same way, the password must have been entered in thebatchfile for deleting DB components for Oracle.

Note: In the local <WINDOWS_NT> directory, the fileWMInst.log is created, which describes the actions executed inthis setup (File is possibly created under C: ).For a possible error solving, it is recommended to save this file (forexample to move it to the windream application directory).

List of windream server logfiles and diagnosticoutputs

windream InstallationFilename Created by<WINDOWS>\wminst.log windream Server

installation/update

<WINDOWS>\wmosinst.log windream ObjectStoreinstallation

%TEMP%\wmosinst.log windream ObjectstoreInstallation

Table 1-2: windream Server Logfiles: windream Installation

1-52 Installation check

windream and MS SQL ServerFilename Created by<WINDOWS>\sqlstp.log Microsoft SQL Server Installation

%TEMP%\sqlsp.log Microsoft SQL Server ServicePack Installation

%TEMP%\mssearch.log Microsoft Search

%TEMP%\wmsql.log windream SQL Server Installation

<windream>\DB\<timestamp>CreateDb.log

windream-Server Installation /osql-log for Create Database

<windream>\DB\<timestamp>CreateFt.log

windream Server Installation /osql-log for Create Fulltext

<windream>\DB\<timestamp>CreateFtSched.log

windream Server Installation /osql-log for creation of fulltextschedules (Version 2.0.1.39 ff.)

<windream>\DB\<timestamp>DBSchema.log

windream Server Installation /osql-log for Create windreamDbScheme

<windream>\DB\<timestamp>WMInitDB.log

windream Server Installation /windream log for Init-DBfunctions

<windream>\DB\<timestamp>WMInitUpdateDB.log

windream Server Update /windream log for Init-DBfunctions

<windream>\DB\DatabaseActions_<timestamp>.log

windream server update / log ofthe database events for updatingthe database.

Table 1-3: windream Server Logfiles: windream and MS SQL Server

windream and OracleFilename Created by<windream>\DB\<timestamp>_cr_role_user.log

windream Server Installation /sqlplus log for Create User

<windream>\DB\<timestamp>_cr_ctx.log

windream Server Installation /sqlplus log for Create Database

<windream>\DB\<timestamp>_cr_grant_ctx.log

windream Server Installation /sqlplus log for Create Fulltext

<windream>\DB\<timestamp>_cr_job.log

windream Server Installation /sqlplus log for CTX-Rightsassignment

<windream>\DB\<timestamp>_cr_sbx.log

windream Server Installation /sqlplus log for creation of fulltext


Filename Created byindexing jobs

<windream>\DB\<timestamp>_upd_db.log

windream Server Update /windream log for Oracle DBUpdate

Table 1-4: windream Server Logfiles: windream and Oracle

Outputs while operating windreamFilename Created by<windreamTempDir>\WMFT.log

windream Server Fulltext-Serviceruntime log

<windreamTempDir>\MM-Tcp.log

windream Server TCP-Serviceruntime log

%MMUNIXLOG%\MM-Arc.log windream Objectstore Archive-Service runtime log

%MMUNIXLOG%\MM-Dam.log windream ObjectstoreDiscAccessManager runtime log

Table 1-5: windream Server Logfiles: while operating windream

General OutputsFilename Created byNT event-log System

Application + System for source:windream DMS-Service

WMTrace.txt Windream extended messagebox

Here, the extended messagedisplay function has to be enabledin the windream Configuration(tab page Messages, option Extendederror display). If necessary, displayederror messages (for example whenenabling the Filter tab page) are tobe confirmed over the Cancelcommand button.

Table 1-6: windream Server Logfiles: general outputs

winwinwinwindreamServerServerServerServerBasicBasicBasicBasic

ConfigurationConfigurationConfigurationConfiguration

2

Basics 2-1

Basic windream ServerSettingsBasics

In this chapter, the basic configurations and system settings aredescribed, which are to be executed after each windream installation onthe respective application server (server on which the windreamservices, the database and the fulltext service are installed). Dependingon the current system architecture, this may be important for one orfor several servers.

The settings are also necessary, if an update of the windream serviceshad been executed after an uninstallation process with a following newinstallation.

Setup will automatically configure specific settings during theinstallation of the windream Server services. A separate dialog box isdisplayed for configuring and creating the windream mainuser accountand the windream group of all windream users. All further settingswhich are automatically executed by the setup do not require anyadditional entries.

The following configurations and system settings are to be configured:

• Assign the operation system rights Log on as Service, Logon as batchprocessing job and Act as part of the operating System to the windreammainuser (automatically assigned by setup).

• Set DCOM configuration for the windream DMS service and forthe Thumbnail service (automatically executed).

• Determine the windream services (DMS, Fulltext, Agent, EventService and Thumbnail Service) in the system settings(Programs>Administrative Tools>Services). This is automaticallydetermined for the DMS Service, the fulltext service and the Agent.The services can be started automatically after having completed theinstallation.

• Check and adjust settings in the windream Configuration.• Enter a windream event in the Scheduled Tasks folder of the

Windows Explorer, which regularly contacts the windream Agent tolaunch actions executed by the Agent (automatically initiated bySetup).

• If necessary, set fulltext option to Language Neutral (SQL Serveronly).

• Configure an SQL Server schedule for fulltext population(automatically created by Setup).

2-2 Basics

• Configure Oracle job for fulltext indexing (Oracle 8i only, notautomatically initiated by Setup). This has to be executed manuallyafter the Setup routine has finished (see chapter on Oracle job forfulltext indexing).

• Assign windream rights for the root directory of windream. Thiscan only be executed with a connected Client computer.

Further requirements for operating windreamIn addition to the system configurations mentioned, further settings arerequired for the operation of windream in the user and groupadministration of the operating system and in the windreamManagement Console. These settings are not executed by Setup andmust thus be executed manually on the respective Servers.

Settings in the user and group administration of the operatingsystemIf you have created a new group for the windream users when runningthe Setup routine, you will have to assign all users to this group whoshall get access to windream. This assignment is executed over the userand group administration of the operating system and on the Server onwhich the group has been created (see also topic "User and groupadministration" in chapter 3 of the windream administration guide).

Settings in the windream Management Console (WMC)After the installation, different configurations are to be made in thewindream Management Console before starting the windreamoperation. These settings must be executed on the windream Serverunder the account of the windream Mainuser. Thus, on the windreamServer, you log in locally as windream Mainuser and start the WMC.You will have to configure the following settings with the repsectiveadministrative functions:

• Apply the user and group acounts from the operating system, whichshall have access to the DMS.

• Determine at least one windream Administrator group in thewindream user and group administration.

• Adjust users and groups.• Create the desired ObjectStores in the administration of the

windream Storages.• Create the required document and folder types with the

administration of object types (determine indices, ObjectStores andLife-Cycle).

2-3

The description of these functions is not part of this documentation.Respective information can be found in the windream user guide andin the administration manual.

Operating system rights for the windream mainuserThe following operating system rights must be assigned to thewindream mainuser:

• Log on as service;• Log on as batch processing job and• Act as part of the Operating System.

Additionally, the windream Mainuser must be assigned to the local OSadministrator group. This assignment is necessary to ensure the correctsystem service processing, especially starting and closing the windreamAgent.

The settings are executed over the user and group administration of theoperating system (for example via the user manager for domains underWindows 2000 in the local security settings).

Note: Setup automatically creates the windream mainuser accountaccording to the entries made during the installation, andautomatically assigns the rights of logging in as Service, logging inas batch processing job and acting as part of the operating system.The assignment of the mainuser to the local OS administratorgroup is executed by the Setup routine, too.The settings will only have to be made manually, if you want tochange the configuration after having finished the installation.

2-4

DCOM configuration for windream DMS service andthumbnail service

You determine the required DCOM configuration for the windreamDMS service and for the Thumbnail service in the DCOMconfigurations.

Note: The DCOM configurations for the DMS service and theThumbnail service are set automatically by the setup routine.These settings will only have to be changed manually, if you want tochange the configuration after having finished the installation. Therequired DCOM-settings are described for the DMS-Service (seebelow). The settings are the same for the Trhumbnail Service.

How to start the DCOM configuration for the windreamDMS service

1. Choose the command Run of the Windows Start menu. 2. Entry dcomcnfg into the input field and activate the OK button.

Windows 2003 Server: 3. In the component services, open folder DCOM Configuration

(Console root>Component services>Computer>Workplace>DCOMConfiguration).

4. Select entry windream DMS-Service from the list ofapplications.

5. Double click the Properties entry to open dialog box Properties ofwindream DMS Service

Windows 2000 Server 6. Choose the entry windream DMS-Service in the list

Applications. 7. Open the dialog box windream DMS-Service Properties via a double

click on the entry or via the command button Properties.

DCOM configuration for windream DMS service and thumbnail service 2-5

Figure 2-1: Properties of the windream DMS Service– Tab Page General

On the tab pages, the required adjustments for the DMS service haveto be executed. If the windream Mainuser account has been configuredas domain user or if the windream user group has been configured asdomain group, you will have to replace <LOCALSERVER> by<MYDOMAIN>, when entering the user accounts for configuring theaccess rights.

Tab page LocationOn this tab page, please check the adjustments which have beenexecuted during the installation by the setup program on the tab pageLocation (Windows 2000). The option Run Application on this Computerhas to be activated. If this is not the case, activate this option with aclick on the respective check box.

2-6 DCOM configuration for windream DMS service and thumbnail service

Figure 2-2: Properties of the windream DMS Service – Tab Page Location

Tab page SecurityOn this tab page you determine the required user-defined access rights,the rights of starting and the configuration rights for the users andgroups.


Figure 2-3: Properties of the windream DMS Service – tab page Security

How to configure user-defined launch permissionsLaunch permissions 1. On tab page Security, highlight option Customize in group Launch

Permissions. 2. Click Edit to open dialog box Slaunch Permisssions.


Figure 2-4: Configuring launch permission for users and groups

3. If entries are existing in group or user name list, you highlight thefirst name in the list and click Remove.

4. Repeat this step until you have removed all entries from the list. 5. Click OK, to confirm the settings.

Note: No entries may exist in the list of user and group names. Ifthere are entries, these will have to be removed.

How to configure user-defined access permissionsAccess permission 1. Enable the Customize option in group Access permissions on the

Security tab page. 2. Click Edit to open the access rights dialog.


Figure 2-5: Changing access permissions for users and groups

3. Click Add to open the dialog box for selecting users and groups. 4. Select the user account of the mainuser

(<LOCALSERVER>\windream or<MYDOMAIN>\windream) and the account of the windreamuser group (<LOCALSERVER>\windream.

5. Add the selected user and goup accounts to the list. of accesspermissions.

6. Assure that the Allow checkmark is clicked.


Figure 2-6: Configuring the access permission

7. Click OK to apply the settings.

How to configure the user-defined configurationpermissions

Configurationpermissions

1. On tab page Security, enable option Customize in group Configurationpermissions.

2. Enable the Edit button to open the dialog box for changing theconfiguration permissions.


Figure 2-7: Configuring the configuration permissions for users and groups

3. If there are more entries existing in the list than the two forAdministrators and Users (Windows 2000: Each), youselect the first entry and click Remove.

4. Repeat this step until you have removed all entries which are notrequired.

5. Click OK to apply the settings.

Note: This setting will not be made by the Setup programautomatically. The two entries for Administrators (allowVfull access) and Users (allow reading) must be available tobe able to make configurations at all.Further settings are reserved for system administrators.

Tab page IdentityOn the tab page Identity you determine the user who is allowed toexecute the windream DMS Service (windream Mainuser).


Figure 2-8: Properties of the windream DMS Service – Tab Page Identity

How to determine the user who is allowed to execute theDMS service

Identity 1. Click option This user. 2. Click Browse. 3. Select the entry for the windream mainuser<LOCALSERVER>\windream or<MYDOMAIN>\windream in the following dialog box forfinding users.

4. Enter into the field Password the password for the windreammainuser, which you have determined during the creation of thewindream user accounts (see also at section “Configure windreamUsers “ in chapter “Installation of the windream server services“).

5. For confirmation, enter once again the password of the windreammainuser into the field Confirm Password.

6. Activate the command button Apply or OK to save theadjustments.

Note: For the entry of the user in the field User, it is recommendedto use the selection help over the user lists of dcomcnfg(command button Browse) in order to avoid incorrect entry.


Note: After a new-installation of windream during which thewindream group “windream user” is created, the installing user(e.g. “administrator”) is not allowed to use the windream serviceson the Server. He will receive the error message 0Χ80070005(access denied) e.g. when selecting the tab page Filter of thewindream configuration or when opening the windreamManagement Console.In order to be able to use and administer the windream Services asinstalling user (for example "Administrator"), the user must bemember of at least the windream groups named windreamUser (the group of all windream users) and of the windreamAdministrator group.Thus, after having completed the installation, you will have toassign the users to the respective groups in the user and groupadministration of the operating system. After that, these groupsmust be taken over into the user and group administration ofwindream, the administrator group must be determined and theadjustment must be executed. These configurations are to beexecuted under the user ID of the windream Mainuser (see alsotopics "Create windream Group Accounts", "Configuringwindream user accounts" and "Further Requirements for theOperation of windream“ in chapter 1 and 2).

Closing the DCOM configuration dialogAfter you have executed all listed adjustments, close the dialog boxesfor the DCOM configuration.

2-14 Adjustments in the administration - services

Adjustments in the administration - servicesThe windream Services have to be configured in the Windows systemadjustments. Depending on the system architecture, the single servicescan be installed on one or several (at most 3) servers. If the windreamObjectStore Service is not installed on the same server on which thewindream main services are installed, you have to execute the followingdescribed configurations for the windream ObjectStore Service on thisserver.

Note: The configuration of the Windows system settings for thewindream DMS Service, the windream Fulltext service, the Agent,the Event Service and the Thumbnail Service are automaticallyexecuted by the setup program.

Setup creates the windream mainuser account according to theentries made during the installation (Login and identification). Thisidentification is used for the configuration of the startup of thewindream DMS Service, the windream Fulltext Service, the Agent,the Event Service and the Thumbnail Service in the system settings(Start>Programs>Administrative Tools >Services). The services are notstarted automatically by the setup. The services can be startedautomatically by the Setup routine.

The configuration of the windream ObjectStore Service (only, if itis installed) and the windream TCP Service in the system settingshave to be executed after the installation as described below. Afterthat, all services are to be started (if this has not been executed yet),either by using the batch file <windream ProgramDirectory>\resource kit\startservices.bat, viacommand Start>Programs>Administration>Services or via thewindream Service Manager from the windream Control Center.

For the configuration of the services, you call the dialog box Serviceswith the command Start>Programs>Administrative Tools>Services. Theservices with the status and the startup are displayed in a list.

Determine the respective adjustments step by step for the windreamServices and start the services:

• windream ObjectStore Service (only, if installed)• windream DMS Service• windream Thumbnail Service• windream Event Service• windream Agent• windream TCP Service• windream Fulltext Service.

Adjustments in the administration - services 2-15

Note: The ObjectStore service and the windream Services(Fulltext-Service, TCP-Service, DMS-Service, Agent, Event Serviceand Thumbnail Service) as well as possible HTML- and VFS-Service for testing can also be started via a batch file. Thus, youlaunch the startservices batch file from the installation directory ofthe windream Server (<windream programdirectory>\ResourceKit\) after having configured thestart type of the services. This file will start the services.

In this batch file, the net-command is used by default to start theservices. If the services are not launched quickly enough and ifnet.exe does not use a configurable timeout to wait for the "started"status, this may lead to problems (e.g., the batch process iscancelled and some services cannot be started). In this case, you canuse module windream WMScm.exe for starting the services. It canbe found in the ResourceKit subdirectory of the windreamCD. The tool has configurable timeout parameters. Thus, in theatch file, set line SET USEWMSCM=true and copy moduleWMScm.exe from the subdirectory ResourceKit to thedirectory in which the startservices.bat has been placed.The timeouts can be configured in the respective variablesLONGWAIT, MEDIUMWAIT, SHORTWAIT or forward themdirectly in the launch processes.

You can also start the windream services from the windream ServiceManager from the windream Control Center.

Figure 2-9: Starting the windream Services

How to determine the adjustments for the windreamservices

windream DMSservice

1. In the Services dialog box, you select the entry of the Service to beconfigured (for example windream DMS-Service.

2. Open the Properties dialog box via context menu.

2-16 Adjustments in the administration - services

Figure 2-10: Configure Services – windream DMS Service

3. Select the automatical option on the General tab page (dropdownlist named Startup type).

4. Switch to the tab page for registering (Log On). 5. Enable option for This Account. 6. Switch to the General page and enable the start button to start the

windream Service. 7. Click OK to apply the settings and to close the dialog box.

Note: For the TCP-Service, the option to log on as a local systrmaccount must be enabled on the Logon tab page.

How to eventually change the pre-adjusted user account

1. Click . 2. Choose the entry <LOCALSERVER>\windream or<MYDOMAIN>\windream for the windream mainuser in dialogbox Add User.

Adjustments in the 2-17

3. Enter into the field Password the password for the windreammainuser, which you have determined during the creation of thewindream user accounts (see also section “Configure windreamUsers “ in chapter "Installation of the windream Server Services.

4. For confirmation, enter once again the password of the windreammainuser into the field Password confirmation.

Note: For entries in the User field we recommend to use thedcomcnfg user lists (Browse button) to avoid incorrect entries!

How to determine the adjustments for the windreamObjectStore service

windreamObjectStore service

This service should already have been started (status started) andAutomatic should be entered as startup. If this is not the case, thenpossibly an error occurs by the installation of the ObjectStore. You canfind information on this in the logfiles mm-arc.log and mm-dam.log for the ObjectStore in the directory <ObjectStorePath>\log or in the documentations according to theobjectstore.

Adjustments in the windream configurationIn the windream configurations you can check and – if necessary -make the adjustments executed by the setup program duringinstallation.

For this, you start the windream Control Center over the commandStart>Programs>windream>Control Center. The windream symbol isdisplayed in the task bar. After that, you start the windreamconfiguration with a double click on the windream symbol or over thecommand Configuration in the context menu (right mouse button on thewindream symbol in the task bar).

User has to bewindream userto start theControl Center

In order to be able to start the windream configuration, the currentlylogged-in user (e.g. administrator) has to be assigned to the group of allwindream users.

Note: After a re-installation of windream during which thewindream group “windream user” is created, the installing user(e.g. “administrator”) will not be allowed to use the windreamservices on the server. He will receive the error message0Χ80070005 (access refused) e.g. when selecting the tab pageFilter of the windream configuration or when opening thewindream Management Console.

2-18 windream configuration

In order to be able to use and administer the windream Services asinstalling user (for example "Administrator"), the user must bemember of at least the windream groups named windreamUser (the group of all windream users) and of the windreamAdministrator group.Thus, after having completed the installation, you will have toassign the users to the respective groups in the user and groupadministration of the operating system. After that, these groupsmust be taken over into the user and group administration ofwindream, the administrator group must be determined and theadjustment must be executed. These configurations are to beexecuted under the user ID of the windream Mainuser (see alsotopics "Create windream Group Accounts", "Configuringwindream user accounts" and "Further Requirements for theOperation of windream“ in chapter 1 and 2).

windream configuration 2-19

Figure 2-11: windream Configuration

Check the adjustments or eventually execute the necessary adjustmentson the tab pages.

Now, the indications which have to be checked are listed. You can finda detailed description of the adjustments of the tab pages in the onlinehelp, which you can call over the command Help in the windreamControl Center.


Tab page ConnectionsOn the tab page Connections you can check the settings executed in thesetup for the connections with the SQL Server or the Oracle database(Database Server Name, Oracle Net8 service name Provider and nameof the windream Database) and for the TCP-Service (TDI Port).

Note: If you have made changes, you afterwards have to stop thewindream Services and start them again (via the service managerfrom the windream control Center, via commandStart>Programs>Administrative Tools>Services or with the help of theBatch files stopservices.bat and startservices.batof the resourekit directory in the windream programdirectory).

Tab page FilterOn the tab page Filter the file filters preset by the setup have to bechecked. In the four groups

• Indexing Events• Recovery of deleted documents• Temporary storage of indices• Fulltext

Call up the single dialog boxes, in which you control and eventuallycustomize the pre-adjusted file filters over the respective commandbuttons.

Indexing events Here the file filter used at the workstations is determined. For the filetypes, which are determined in the filter, the respective IndexingEvents are automatically sent to the workstations during the acquisitionor the transfer of documents in the DMS. The file filters are configuredin two lists, a positive and a negative list. This means that those filetypes are determined which are included or excluded from beingindexed.

On the right side, you have to indicate (list Documents NOT to be indexed)all filters for – for example – temporary files (e.g.: *.TMP), for whichIndexing Events should not be sent to the workstations, whereas thelist on the left determines which types are to be indexed.

Note: These lists are pre-adjusted during the installation of thewindream Server by the Setup program, and normally it is notnecessary to change them.

In the group Indexing Events, further adjustments for the indexing


service of windream have to be checked, too.

In order to ensure that Indexing Events are created corresponding tothe further adjustments for the indexing service and are sent to theworkstations, you have to take care that the ckeckboxes Send Jobs andActivated are enabled.

If Indexing Events shall also be created for directories and if they shallbe sent to the workstations you have to activate the option also forfolders.

Recover deleteddocuments

Here, the file types for which windream does not save the recoveryinformation for the recovery function (Recovery-Tool) in thewindream Management Console (WMC) are determined.

Note: This list is pre-adjusted during the installation of thewindream Server by the Setup program, and normally it is notnecessary to change it.

Temporary storageof indices

Here, the processes are determined for which windream does not saveany information for the temporary storage of indices.

Note: In the list of the processes for which a temporary storage ofindices is not executed, the entries explorer and winfilehave to be entered.This list is pre-adjusted during the installation of the windreamServers and it is recommended not to change it.

Fulltext Here, the file types are determined for which the fulltext populationover the windream Fulltext Service shall be started. The extractionsoftware is assigned on the fulltext tab page.

Note: During the windream Server setup, this list is pre-adjustedby the setup program. If the fulltext population for further filetypes shall be started, the file filter has to be extended accordingly.

Possible problems when configuring settings on tab pageFilterWhen switching to the tab page Filter for configuring the file filter, thesystem automatically connects the windream DMS Service. In case thatproblems should occur in this process, a respective message isdisplayed. For a detailed error analysis and a solution of the problem,you will have to switch to the extended error display.

Thus, you switch to the windream configuration and from there to thetab page Messages. Enable the option Extended Error Message in the groupDialog Output. Close the windream configuration with OK. After that,


open the windream configuration once again and switch to the tabpage Filter.

If now an error again occurs in the connection to the windream DMSService, open the extended error display by clicking Cancel and switchto the tab page Details in order to receive further information on thecurrent error (click Details to display all current errors).

You can save error loggings in a file if you enable the Save command.

Tab page LicencesHere, the license data are to be checked. If incorrect entries were made,no entries will be visible except the user data, and an error message isdisplayed when the tab page Licences is activated.

If incorrect entries have been made, you can correct these entries bydouble clicking the folder User data for editing the respective data in adialog box. In this dialog box you can make the desired changes. Youcan copy the respective license data from the WMCustom.ini filewhich you received from your partner, if you enable the commandbutton From file.

Note: Please ask your supplier or your partner from whom youpurchased windream (Hotline) for support in case of errors.

You will receive the license key according to the current license datafrom your partner or the supplier. You enter this key during theinstallation of windream. In the field Key, the current license key whichis valid for you is displayed. You will get another key to be entered andsaved here, if the license data changes, for example when the numberof licenses is extended.

Note: If you change entries, you will have to stop the windreamservices afterwards and start them again (via the service managerfrom the windream Control Center, via the commandStart>Programs>Administrative Tools>Services or with the help of thebatch files stopservices.bat and startservices.batof the windream program directory).

Tab page FulltextOn the tab page Fulltext, the schedule for the fulltext population has tobe checked and the logging settings of the fulltext service. Additionally,you determine the extractor modules here for the file types to createthe fulltext.


Try new connectionafter (sec)

Here, the time interval is entered according to which the windreamfulltext service tries to connect again to the windream DMS service(database service). Then, the system searches for documents for whichfulltext shall be populated in the database. The default value is 900seconds. In case the connection fails (for example if the windreamDMS service is not started), the windream DMS service tries toconnect repeatedly.

Start new searchafter (sec)

Here, the time interval is determined according to which the fulltextservice searches for new or changed documents. The preset value is300 seconds which means that windream enables the fulltextpopulation every 5 minutes.

Timeout perdocument (sec)

Deafult value is 3600 seconds. Within this period, the fulltext servie willtry to extract the fulltext from a document. E.g., this timeout can bereached in OCR processes of large documents or when problems occurwith the OCR software. If the timeout is reached, the document will bemarked in the history, and the fulltext extraction will be cancelled. Thefulltext service will close itself on security reasons and will start again.Generally, timeouts of 10-30 seconds should be sufficient.

Note: If preset times shall be changed, the windream fulltextservice has to be terminated and started again afterwards (via theservice manager from the windream Control Center or viacommand Start>Programs>Administrative Tools>Services,)(see section"Adjustments in the Administration - Services“, page 2-14).

Trace options According to the trace options you determine the details of logging. thetrace options can be changed for trouble shooting or error tracing.Options +fatal+error+warning are preset.

Logfile Indicates the path of the logfile of the windream fulltext indexingservice.

File type assignment This button will open the dialog box for editing the list. You candetermine a software to be used for the extraction for each file type.

Tab page CommonOn the tab page Common you determine the global script directory.

Set global scriptdirectory(if needed )

In the field Global Script Directory, the global directory is entered inwhich the available scripts on the server are saved to be used by allworkstations (Visual Basic or Java Scripts). There are two differentways of possible settings:

• Fully qualified with drive letter ("normal" network drive). In thiscase, it must either be a drive of a file server which is generallyavailable at the workstations, or, if this path points towards a


directory in the windream drive, all workstations must haveconfigured the same drive letter for the windream drive (this isgenerally recommended in any case).

• Without drive letter (directory in the windream drive). In this case,the path always points towards a windream directory, and allworkstations can launch these scripts, even if the windream drive isconfigured on different drive letters.

Annotations In this section you determine the object type to be used by windreamfor storing annotations. This object type must exist in windream. Ifrequired, you will have to create an object type using the functions ofthe windream Management Console (see also "Administeringannotations" in chapter "Further windream services, Service Managerand System Monitoring" (windream Administration guide)).

In the field for determining the annotation directory, you enter thebasic folder (without drive letter) in which windream shall place theannotations. This folder must be a directory of the windream drive. Inorder to enable windream to save annotations there, you will have tocreate a folder in the windream drive with the name entered here, e.g.System\annotations.

Settings for scheduled tasks 2-25

Settings for scheduled tasksA windream process will be entered in the Scheduled Tasks folder ofthe Windows Explorer, which will regularly contact the installedwindream Agent in order to initiate scheduled tasks to be executed bythe Agent. The task configured here is named Archive and delete windreamobjects. This task will execute life-cycle processes, for example movingdocuments to an archive storage area or delete them from the database.

Note: The configuration of scheduled tasks – as described in thepresent chapter – will automatically be excuted by Setup.

This task must be configured as "Execute as" windream mainuser (theuser account which has been determined for the mainuser during theinstallation (<LOCALSERVER>\windream or<MYDOMAIN>\windream.

In order to check settings, you open the scheduled tasks folder viaStart>Settings>Control Panel and select the entry for archiving anddeleting windream objects. Select the command Properties from thecontext menu. The command "Execute as"<LOCALSERVER>\windream or <MYDOMAIN>\windreammust be entered in the tab page Task (field Execute as).

SQL Server schedule for fulltext populationA schedule has to be created in the Microsoft SQL Server EnterpriseManager for the population of fulltext.

A fulltext search in windream is only possible after the database hasfinished the fulltext indexing. The windream fulltext service executesthe fulltext extraction and puts the textas into the databaase. Then, theschedule set in the fulltext catalog named windreamft will be executed.Only then will the fulltext be retrievable.

Note: The configurations for creating the SQL Server schedule forthe fulltext population – as described below – are automaticallyexecuted by Setup.Settings must only be made manually, if you want to change theconfiguration after having completed the installation.

If you use Microsoft SQL Server 2000, the fulltext population mayalso be executed as a remote service and as an alternative via theSQL Server 2000-specific setting of the remote index update(recommended). The required configurations must be mademanually (see chapter "Index Update in Background for SQLServer 2000"), p. 2-30).

2-26 SQL Server schedule for fulltext population

In order to determine this schedule, you start the SQL ServerEnterprise Manager with the command Start>Programs>Microsoft SQLServer>Enterprise Manager.

Figure 2-12: SQL Server Enterprise Manager

Creating a new scheduleAfter that, you switch to the folder Console Root>Microsoft SQLServer>SQL Server Group><windream DB-Server> and open the folderDatabases>windream>Fulltext-Catalogs.

Figure 2-13: SQL Server Enterprise Manager – Folder Fulltext Catalog

How to create a new schedule

1. Select the catalog windreamft in the folder Fulltext Catalog. 2. Open the context menu and choose the command Schedules.

SQL Server schedule for fulltext population 2-27

Figure 2-14: Schedules for Fulltext Indexing

3. Enable the New Catalog Schedule button on the tab page Schedules.

Figure 2-15: Create New Schedule for Fulltext Population


4. Enter a name for the new schedule in the field Name. 5. Ensure that the checkbox Enable is marked. 6. Select the radio button Incremental population in the group named Job

type. 7. Select the radio button Recurring in the group Schedule frequency. 8. Enable the Change button to open the dialog box Edit Recurring

Fulltext Indexing Job Scheduling – windreamft.

Figure 2-16: Create New Schedule for Repeated Fulltext Population

9. Select the radio button Daily in the group Occurs. 10. Choose the radio button Occurs once at in the group Daily frequency. 11. Enter the point of time in the dialog box Occurs once at for which

the fulltext population shall be executed. 12. In the group Duration you select the radio button No end date. 13. If necessary, modify the starting date in the field Start date. The

date is preset with the current date. 14. Close the dialog box Edit Recurring Fulltext Indexing Job Scheduling -

windreamft with the OK button. 15. Enable the OK button to close the dialog box New Fulltext Indexing

Catalog Schedule – windreamft.

SQL Server schedule for fulltext population 2-29

Figure 2-17: Schedules for Fulltext Indexing.

16. Click OK to save the new schedule and to close the dialog boxFulltext Indexing Schedules – windreamft.

Note: During a test run, the frequency of the fulltext populationcan also be set on “several times a day” (for example every 30minutes). This is executed over the button Everyone in the groupDaily frequency Tag in the dialog box Edit Recurring Fulltext Indexing JobScheduling - windreamft).The currently created schedule is only kept upright, meaning thatthe population is started, if in the Control Panel Services theSQLServer-Agent is started. It is recommended to set the typeof start for the SQLServer-Agent service on Automatic.You can make this setting just like the respective settings for thewindream Services over the commandStart>Programs>Administrative Tools>Services in the dialog box Services(see section "Adjustments in the Administration - Services“, page 2-14).


Remote index update under SQL Server 2000In order to achieve a near realtime fulltext creation in SQL Server,Microsoft recommends for SQL Server 2000 to use the change trackingsetting and to update indices remotely instead of the incrementalpopulation of the fulltext catalog.

How to configure the index update in background

1. Start the SQL Server Enterprise Manager via commandStart>Programs>Microsoft SQL Server>Enterprise Manager.

2. Switch to folder Console Root>Microsoft SQL Server>SQL Server-Group><windream DB-Server> and open folderDatabases>windream>Tables.

3. Select the Fulltext entry in folder Tables. 4. Open the context menu and click command Fulltext index table. 5. Select the change tracking command from the submenu Thecontext menu will be suppressed.

6. Open the Fulltext index table submenu again (command Fulltextindex table>Change Tracking from the context menu). The changetracking is active now (checkmark in front of the command).

7. Now, select option Update Index in Background to switch thisfunction on.

The existing schedules for the windream fulltext catalog (windreamft)responsible for the complete and incremental population can then bedeleted.

Thus, switch to folder Console Root>Microsoft SQL Server>SQL Server-Group><windream DB-Server> and open folderDatabases>windream>Fulltext catalogs. In folder Fulltext catalog, selectcatalog windreamft and delete the schedules with the respectivecommands from the context menu.

Further notes can be found in the respective documentations byMicrosoft, e.g. under

http://msdn.microsoft.com/sql/default.aspx?pull=/library/en-us/dnsqlpro04/html/sp04f9.asp

(10 Ways to Optimize SQL Server Fulltext Indexing -> Use changetracking with the "update index in background" option).

Oracle jobs for fulltext indexing 2-31

Oracle jobs for fulltext indexingAn Oracle job will be configured by the Server setup for the fulltextindexing, which synchronizes the fulltext index every 5 minutes andthus makes it retrievable.

Note: The configuration described below for the Oracle fulltextindexing jobs are not executed automatically by the setup.The settings required will have to be made manually after theinstallation if you use Oracle 8i. In Oracle 9i, the option is set bydefault and need not be adjusted.

In order to execute this job, the Oracle Standard Edition and theOracle Enterprise Edition as well the settingjob_queue_processes = 2 must be set.

This setting can for example be made before starting Oracle in therespective initialising file. In order to find out whether this entry existsin the file or to set it, you can trace the initialising file used as follows:

Search the following entries in the registry of the computer) using theregedit.exe command) on which the Oracle database is installed:

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEx\ORACLE_SID = <oracle_sid>

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEx\ORA_<oracle_sid>_PFILE = 'intialisation-file'

for example:

ORACLE_SID = oracle8service

ORA_ORA8HOB_PFILE ='D:\OracleDB\oracle8service\pfile\init.ora'

open the initialising file <Inifile>.ora (for exampleinit.ora) in a text editor. The line job_queue_processes= 2 must exist in the file. If it does not exist, you can add it manually.

After having entered or changed this value, the database must berestarted via DBA Studio. Please note that the correct initializing file isused on startup.

2-32 Assigning windream rights to root directory

Assigning windream rights to root directoryThe assignment of rights for the windream root directory (windreamdrive), the creation of the initial folders and the assignment of rights forthese folders according to the different user groups is executed on aconnected windream client.

By default, the rights of reading, writing and assigning rights is assignedto a windream user group and is set for the windream root directory ofthe windream drive. The initial settings are made by one member ofthis group, which usually is the windream mainuser.

In version 4.0, the windream Business Edition provides an enhancedrights concept. This way, it is e.g. possible to assign separate rights tofolders and contained documents (besides the common rights heritage).You can also assign separate rights for index and original file or youcan restrict the rights of reading specific documents.

By default, all rights including the right to assign rights are set for awindream user group concerning the windream root directory inwindream BE. However, this only refers to the default rights heritageconcerning folders and contained objects (option folder rights).If a separate heritage of rights according to file and folder rights isdesired, you will have to assign the inheritable file and folder rights forthe respective folders.

RECOMMENDATION:

Create the main folders which are most important for your companyon the root level of the windream drive and assign initial rights to thesefolders. After that, you remove the rights of editing (NOT the rights ofreading!) from the root level for all windream groups except the admingroup. This process prevents the creation of temporary files by mistakeor a non-coordinated creation of folders in the root directory, when thesetup routine is executed.

Further on, it is explained now how to assign initial rights. You willfind a detailed description of the administration of rights in the onlinehelp and in the windream administration and user guides (cf. topic"windream rights").

How to assign initial rights to the windream root directory

1. Log in as windream mainuser at a connected client (installation ofwindream client software is required.

2. Start the windream Services (VFS-Service). 3. Select the windream drive. 4. Enable the Properties command over the context menu. 5. Switch to tab page Rights.

Assigning windream rights to root directory 2-33

6. Assign the required rights to the respective user groups by addingthe desired groups and setting the rights via the respectivecheckmarks.

7. Click OK to apply the settings and to close the dialog box.

Abbildung 2-18: Assigning windream rights to root directory

After that, you switch to the windream drive and create the necessaryfolders there. Then, you assign the rights on these folders to therespective user groups like you did for the root directory.

windreamwindreamwindreamwindreamServerServerServerServer

UninstallationUninstallationUninstallationUninstallation

3

Uninstalling the ObjectStore service 3-1

Uninstalling the windreamServer ServicesUninstalling the ObjectStore service

Before uninstalling the windream Server services, the windreamObjectStore Service has to be closed. An uninstallation of theObjectStore is not necessary in any case. However, the uninstallation ofthe ObjectStore should only be executed after the uninstallation of thewindream Server services.

Note: An uninstallation of the ObjectStore service may only beexecuted after having closed the windream Server Services (see"Uninstall windream Server Services", page 3-1).

The description of the uninstallation of the windream ObjectStoreservice is not part of the present documentation. If you want touninstall the windream ObjectStore service, please cf. the detaileddescription in the respective documentation of the windreamObjectStore.

Uninstall windream server servicesAn uninstallation of the windream Services has to be executedaccording to the following steps:

• Close the windream services (Thumbnail Service, Agent, Full-textService, Event Service, TCP- and DMS-Service) by executing file<windream Programdirectory>\resourcekit\stopservices.bat or viaAdministrative Tools>Services or via the windream Service Manager.

• Close the windream Control Center in the system tray of the taskbar.

• If ObjectStore is installed: Ensure that the windream ObjectStoreService is closed, and terminate it – if necessary – AdministrativeTools>Services.

• For MS SQL Server:Via SQL Server Enterprise Manager: delete windream database andwindream database user.

Note: In the directory <windream ProgramDirectory>\DB, a file named dropDB.bat is created duringthe windream installation. When this file is launched, the database,

3-2 Uninstall windream server services

the jobs (SQL Server Agent-jobs) and the database user accountscan be deleted completely.In order to avoid a deletion of the database and the user account bymistake, the respective commands have been disabled (REM). Ifthe database including SQL Server jobs and the user shall bedeleted, the respective commands have to be enabled manuallybefore this file is executed.The generation of launching commands for deleting DBcomponents depends on the settings of the SQL Serverauthentication executed during the setup (see chapter "MS SQLServer Authentication" in chapter 1). If the option SQL-ServerAuthentication was chosen, the password entered there willnot be entered in the call commands of the batch file. In this case,the password has to be entered manually before deleting the DBcomponents (substitute entry <SQLAdminPasswd> bypassword).

For Oracle:

• Via Oracle DBA Studio or the Oracle Enterprise Manager: deletewindream database and windream database user.

Note: In directory <windream Program Directory>\Dba file named dropDB.bat will be created during the windreaminstallation. By enabling this file, the windream database, theconfigured windream database user and the windream fulltextindexing jobs (only Oracle Enterprise Edition) can be deleted.

In order to avoid a deletion of the database and the user by mistake,the respective commands in the file have been disabled (by usingthe REM instruction). If the database including the user shall bedeleted, the respective commands are to be enabled manually again,before the file is executed.

the calls for deleting the DB components are created for the Oracleauthentication, depending on the settings made during the setup(see chapter "Oracle Authentication", in chapter 1). the passwordentered there is not entered in the calls of the batchfiles. For thedeletion of the DB components, the password must have beenentered manually before (substitute entry <SQLAdminPasswd>by password).

• Uninstall windream Server from Control Panel>Software.• Check over button named Details whether there are some

components which could not be removed. If necessary, this listshould be saved in a textfile with the command Cut/Copy/Paste, forbeing able to check whether these files have been removed after areboot of the computer.

Uninstall windream server services 3-3

• Check in folder Scheduled Tasks whether this windream process hasbeen deleted. Otherwise remove it manually.

• In any case, reboot the computer.

Note: The ObjectStore Service and the windream Services(Fulltext Service, Agent, Thumbnail Service, Event Service, TCPService and DMS Service) can also be shut down with the help of abatch file. Thus, you call the stopservices.bat file from theresourcekit subdirectory of thr windream server program directory.The services will be closed then. After that, you will have to deletethe windream database and the windream database user, uninstallthe windream Server (Control Panel>Software) and reboot thecomputer.

Uninstalling the windream server servicesFirst, you shut down the windream Control Center and after that thewindream services in the order presented here. After that, you deletethe windream database and the windream database user. Then, youuninstall the windream Server and reboot the computer.

How to uninstall the windream server servicesClose the windreamservices

1. Execute file stopservices.bat from the resourcekitsubdirectory of the windream server program directory to closethe services automatically.

Or

1. Open the windream Service Manager via command Service Managerfrom the context menu of the windream Control Center.

2. Select entry All windream Services in the list of theServices.

3. Click Close. 4. Close the Service Manager.

Or

1. Open the Services dialog box (e.g via commandStart>Programs>Administrative tools>Services).


Figure 3-1: Closing the windream services

2. Highlight the entry of the first service to be terminated(windream Fulltext-Service).

3. Click the command button for closing the service. 4. Repeat steps 2 – 3 for all services to be closed. 5. Close the Services dialog box.

Close windreamControl Center

1. Close the windream Control Center using the Close command fromthe Context menu of the windream Control Center.

Remove windreamdatabase

1. Execute file DB\DropDB.bat in the program directory of thewindream Server to automatically delete database, jobs of SQLServer Agent or the windream fulltext indexing jobs (only OracleEnterprise Edition) and database user accounts (if necessary,enable commands in the file).

OrDelete the database and the database user with the respective functionsof the administration programs of the database used (SQL EnterpriseManager or Oracle DBA Studio/Enterprise Manager). Steps 1 to 7describe how to delete the database and the database user from SQLServer Enterprise Manager. If you use Oracle, you can proceed thesame way. If you have already removed the database and the databaseuser, proceed with step 1 of chapter "Uninstall windream Server".

MS SQL Server 1. Start the SQL Server Enterprise Manager with the commandStart>Programs>Microsoft SQL Server>Enterprise Manager.

2. Switch to the folder Console Root>Microsoft SQL Server>SQL serverGroup><windream DB Server>Databases.

3. Mark the entry windream and choose the command Delete in thepop-up menu.

4. Confirm the security message displayed with Yes to delete thewindream Database.

Uninstall windream server services 3-5

Figure 3-2: windream Server Uninstallation – Delete windream Database

Delete windreamdatabase user

5. Switch to the folder Console Root>Microsoft SQL Server>SQL ServerGroup><windream DB-Server>Security>User names.

6. Mark the entry for the windream Database User and choose thecommand Delete in the pop-up menu.

7. Confirm the security message displayed with Yes to delete thewindream Database User.

Figure 3-3: Uninstall windream Server – Delete windream Database User

Uninstall windreamserver

1. Open the dialog box of the software properties with the commandSettings>Control Panel>Software in the Windows Start menu.

2. Choose the entry windream Server <Versionnumber>.

3. Enable the button Add/Remove to uninstall the windream Server.


4. Enable the button Details to check whether some of thecomponents could not be removed. It is recommended to save thislist as a textfile with the function Cut/Copy/Paste for being able tocheck whether these files could be removed after the reboot of thecomputer.

5. Open the Scheduled Tasks in the Explorer to check whether thewindream process has been deleted. Otherwise, remove the taskmanually.

Reboot system 6. In any case, reboot the computer.

ImportantImportantImportantImportantNotes onNotes onNotes onNotes on

InstallationInstallationInstallationInstallationandandandand

ConfigurationConfigurationConfigurationConfiguration

4

User account for executing the installation 4-1

In this chapter you will find tips, hints and solutions concerningdifferent problems which might occur during the installation or theconfiguration of windream.

Additionally, the following chapters will assist you in solving errors.

User account for executing the installationAll windream Server installations and configurations are to be executedas user with local administration rights, as services are installed andlocal user and group accounts must be created.

No connection to server (unknown error)After a new installation of windream with which the windream groupnamed "windream users" is created, the installing user (for example"administrator") is not allowed to use the windream Services on theServer. Thus, the error message telling you that there was noconnection to the Server due to an unknown error will be displayedwhen opening the Filter tab page of the windream configuration orwhen opening the windream Management Console.

In order to be able to use and administer the windream Services as theinstalling user (for example "administrator"), the user must at least bemember of the windream groups named windream-users (whichis the group of all windream user) and of the windream Administratorgroup.

Thus, after having completed the installation, you will first have toassign the user to the respective groups in the user and groupadministration of the operating system. After that, these groups mustbe applied to user and group administration of windream, the admingroup must be determined, and an adjustment on the user and groupdata must be executed. Further information can be found under topic"User and group administration" (chapter 3 of the windreamadministration guide).

Note: These configurations are to be executed under the user IDof the windream mainuser.

Context menu unavailable on windream client computerThe windream context menu is nit displayed on a windream client.(version 3.0.13 or higher). In this case, MS Internet Explorer 5.01 withwith ActiveDesktop must be installed. After that, you reboot your

4-2 Error while executing file WMInit.exe

computer (additional hints can be found under topic "Systemrequirements" in the documentation "windream – Client installation").

Error while executing file WMInit.exeIf an error occurs when executing file WMInit.exe during theinstallation process (mainly when using Microsoft Small BusinessServer), the windream Server must be uninstalled and the Setupprocess must be executed again.

In this case, make sure that the authentication mode of SQL Server isselected for installing the windream mainuser and the windreamdatabase in SQL Server (see dialog box SQL Server Authentication of theSetup for configuring the database).

When entering name and password, an available user (for example "sa")must be determined in SQL Server Enterprise Manager under ConsoleRoot>MS SQL Server>SQL Server Group><windream DB-Server>>Security>Username. If user "sa" does not exist, a new useraccount – for example "Administrator" – with Server role SystemAdministrators must be created (Console root>MS SQLServer>SQL Server Group><windream DB-Server>>Security>Username). Seealso chapter "MS SQL Server Authentication" in chapter 1.

Changing the assignment of users to groupsIf group assignments of users are changed in the operating system or ifusers are added to groups, these changes will only become effective inwindream if an adjustment is executed on the respective user andgroup accounts in the windream Management Console. Please alsoconsider notes under topic "Create windream Group Accounts" inchapter 1.

windream DMS service not startedIf the windream DMS Service does not start, or if it is shut down aftera short time, this can have different reasons. The main reasons arelisted now.

Incorrect windream mainuserIn case the windream DMS Service does not start, this may be due toan incorrect or non-existing windream Mainuser:

• NT user (see notes at hints in the installation description, chapter 1"Configure windream Users").

windream DMS service not started 4-3

• SQL Server / Oracle user for windream database (the windreammainuser must have access to the windream database with the samename/password).

• windream ObjectStore Service (the windream Mainuser determinedduring the setup is automatically entered in the user list of thewindream ObjectStore Service).

A check of the windream Mainuser can be executed as follows:

If for example C:\programs\windream GmbH\windreamObjectStore is the installation directory and the windreamMainuser account has been created with the name "windream" and thepassword "xxxxx", the following commands are to be executed in anMS-DOS window:

cd c:\programs\windream GmbH\windreamObjectStore\bin

mmpasswd -check windream xxxxx

If the user is entered correctly, the system will display "OK".

Note: You will get a hint concerning the syntax of the commandmmpasswd by entering mmpasswd –help. The commandmmpasswd displays an accessibility for the call without parameter.Further options for mmpasswd are "-add", "-delete".

Note: A change of the windream mainuser can be executed overWMShdw.exe, which is installed in the windream programdirectory. You start the program via command Advanced>Password-File-Check-Change of the windream program menu. In this dialog, onthe left side, the data determined during the setup (name/password)of the windream Mainuser are to be entered first. Over the Checkbutton, the entries are checked and, if the entry was correct, theinput fields for new entries are enabled. After the renewed entry ofa user name (or a new password only), a message box. Displayedinformation has to be considered URGENTLY (see also "Changingthe user ID of the windream mainuser", page 4-10).Here, the determined user is implicitly authorized to use thewindream ObjectStore Service via WMShdw.exe, if this service islocally installed. Otherwise please consider the notes in chapter 1,"Install windream ObjectStore".The DCOM- and service settingscan then be configured with WMStpCfg.exe from the windreamprogram directory. Please note that correct user and group namesand the correct password of the windream mainuser are enteredthere.

4-4 IP server address changed

Incorrect setting of DCOM configuration /administration - servicesPlease urgently consider the notes in chapter 2 "DCOM Configurationfor the windream DMS Service" and "Adjustments in Administration -Service".

ObjectStore service not configured or not startedIf the windream ObjectStore is installed, it has to be started before thewindream DMS Service. Please consider that the ObjectStore Servicecan also be installed on another computer than on the current one (seechapter 1, "Install the windream ObjectStore" and chapter 2, "TabPage Connections").

windream mainuser unknown to the ObjectStoreserviceDuring the windream setup, the windream Mainuser account is createdas user of the ObjectStore Service in its own user administration. If thisfailed due to unknown reasons (for example because the windreamObjectStore Service had been installed later than the windream Server),the process has to be executed manually. (see information onwmshdw.exe in section "Incorrect windream Mainuser", page 4-3).

Incorrect windream database nameThe database name set in the windream configuration or the OracleNet8 service name does not correspond to the database which wascreated during the setup (state is depending for example on restore of abackup). In this case, the correct database name (respectively OracleNet8 service name) has to be entered in the windream configuration(see chapter 2, "Tab Page Connections"). After that, the windreamServices have to be terminated and started again (commandStart>Programs>Administrative Tools>Services or with the help of thebatch files stopservices.bat and startservices.bat ofthe resourcekit subdirectory in the windream program directory).

Ensure that the windream Mainuser has access to the database whichshall be used.

IP server address changedwindream DMS Service does not start if the IP address of the serveron which the DMS Service is started has changed. A correspondingentry is made in the Windows event log.

Oracle DB instance not yet accessible 4-5

Reason:

Generally, it is possible to configure the DMS Service on anothersystem than on the one on which the SQL Server or the Oracleinstance runs. In order to avoid simultaneous connections of DMSservices of several, but different servers, the IP address of the serverwill be entered into the windream database on first startup of the DMSService.

During further starts of the DMS Service, the IP address will becompared. A connection will be refused if there are differences. Thisprocess avoids inconsistencies caused by the start of the DMS Servicefrom different computers.

Solution:

The respective entry is to be deleted in the windream Database (TableSetting, line: szKey = DMS-Service). This can for example beexecuted via SQL Server Enterprise Manager or Oracle DBA Studio.

How to delete the entry from the settings tableMS SQL Server 1. Switch to folder Console Root>Microsoft SQL Server>SQL Server-

Group><windream DB-Server>. 2. Open folder Databases>windream>Tables. 3. Select entry Setting. 4. Select command Open Table>Show All Lines from the context menu

and select the option for returning all lines. 5. Delete the entry for the IP address in column szIPAddress in

the line for the DMS Service (column szKey = DMS-Service)

Oracle The same procedure can be executed via Oracle DBA Studio or OracleEnterprise Manager.

Oracle DB instance not yet accessibleThis only refers to Oracle database installation. If the windream as wellas the Oracle services are started automatically after a reboot of theServer, the windream DMS Service might not have access to Oracleyet, although all Oracle services are indicated as being started.

In this case, the following error message will be displayed in theWindows event log of the windream DMS Service (which is the sameafter a manual login at the Oracle instance via sqlplus):

ORA-01033 Oracle initialisation or shutdown inprogress

or

4-6 Database not correctly installed

ORA-01034 Oracle not available

Solution:

The number and the delay of login attempts of the windream DMSService to the database are to be configured according to commonexperience on the local Server, so that – after a repeated login – aconnection to the database can be established. These configurations areto be executed in the windream configuration. Thus, you start thewindream Control Center using commandStart>Programs>windream>Control Center. The windream icon isdisplayed in the taskbar. After that, you start the windreamconfiguration with a double click on the windream icon or usingcommand Configuration of the context menu. Switch to tab pageConnections and enter the desired connection parameters (for example 20attempts every 30 seconds). By default, 30 attempts on every 30seconds has been preset.

Database not correctly installedIn case that errors should occur while creating the database/thedatabase user, while initially filling the database or while creating thefulltext components, the created SQL logfiles can be found in thewindream/DB- directory (<windream Program directory>\DB; here, for example an incorrect database admin login will belogged).

In this case, the installation of the components windreamdatabase and/or windream Database FulltextExtension are to be executed again (see chapter 1, "Installwindream Server (Launch Setup)" and "Check Installation").

Before the installation, the windream Services must be terminated andbe started again after a successful installation (over the commandStart>Programs>Administrative Tools>Services or with the help of thebatch files stopservices.bat and startservices.batfrom the resourcekit subdirectory of the windream program directory).This process can also be executed over the windream Service Managerfrom the windream Control Center. After the installation, the settingsfor the connections to the SQL Server (to Oracle Net8 service) have tobe checked in the windream configuration (see chapter 2, "Tab PageConnections").

If necessary, the windream database and the database user have to bedeleted before the installation is conducted. This can be executed fromSQL Server Enterprise Manager or from Oracle DBA Studio / OracleEnterprise Manager via file dropDB.bat.

Database not correctly installed 4-7

Note: In the directory <windream ProgramDirectory>\Db, a file named dropDB.bat will be createdduring the windream installation. By enabling this file, thewindream database, the windream database user and the windreamjobs (SQL Server Agent jobs) or the windream fulltext indexingjobs (Oracle Enterprise Edition only) can be deleted.

In order to avoid a deletion of the database and the user by mistake,the respective calls have been disabled in the file (REM instruction).If the database (including SQL Server jobs or fulltext indexing jobs)and the user shall be deleted, the respective calls are to be enabledmanually again, before the file is executed.

The calls for the deletion of the DB components are generated anddepend on the settings made during setup for SQL Server andOracle authentication (see chapter "MS SQL ServerAuthentication", in chapter 1 or "Oracle Authentication", inchapter 1). If the option SQL-Server Authentication hasbeen selected, the password entered there will not be entered in thecalls of the batchfile. For deleting the DB components, thepassword must be entered manually in any case (substitute entry<SQLAdminPasswd> by password).This is also valid for Oracle, if DB components are to be deleted.

Note: In the local <WINDOWS_NT> directory, a file namedWMInst.log is created, which describes the actions executed inthe setup (file has possibly been stored in C:).In order to execute a possible error logging, we recommend to savethis file (for example to move it to the windream programdirectory).

How to delete windream database and windream databaseuserMS SQL Server

1. Start the SQL Server Enterprise Manager with the commandStart>Programs>Microsoft SQL Server>Enterprise Manager.

2. Switch to the folder Console Root>Microsoft SQL Server>SQLServer-Group><windream DB-Server>Databases.

3. Select the entry windream and choose the command Deletefrom the context menu.

4. Confirm the security message displayed with Yes to deletethe windream Database.

5. Switch to the folder Console Root>Microsoft SQL Server>SQLServer Group><windream DB-Server>Security>User Names.

4-8 windream TCP-service does not start (WSAADDRINUSE)

6. Select the entry for the windream Database User and choosethe command Delete from the context menu.

7. Confirm the security message displayed with Yes to deletethe windream Database User.

OracleDeleting the entries from the table can be done the same way via theOracle DBA Studio / Oracle Enterprise Manager.

Note: In the local <WINDOWS_NT> directory, the fileWMInst.log is created, which describes the actions executed inthis setup (File is possibly created under C: ).For a possible error solving, it is recommended to save this file (forexample to move it to the windream application directory).

windream TCP-service does not start (WSAADDRINUSE) By default, the windream TCP-Service is configured on port 534.This port is reserved for windream and should thus not be occupied byother services. If the port number is nevertheless used by otherservices, the TCP-service cannot be started any more (error in file mm-tcp.log WSAADDRINUSE).

In earlier versions of the windream Server, the TCP-service wasconfigured on port 1122. This port will not be changed during anupdate insatallation on the Server.

Under specific circumstances (depending on the system requirements),it may then happen that this number is used by the local installation ofMS SQL Server or by another application like PC Anywhere. If – inthis case – the windream TCP Service is closed, for example SQLServer occupies the reserved port number and does not release it again.After that, the windream TCP Service cannot be started again (error infile mm-tcp.log WSAADDRINUSE).

In these cases, the port number in Service file(\system32\drivers\etc\Services on the windreamServer ) must be changed (for example to 534). After a restart of thewindream TCP Service, the TDI settings on the workstations must beadjusted respectively (in the windream alias settings via the Serverseelection e.g. via tab page Connections of the windream configuration).

How to change the port number in file Services

1. Open the services file\system32\drivers\etc\Services on the windreamServer.

windream TCP-service does not start (WSAADDRINUSE) 4-9

2. Change entry

mm-tcp 1122/TCP WINDREAM TDI PORT

to:

mm-tcp 6022/TCP WINDREAM TDI PORT

3. Save the changes. 4. Start windream TCP Service again.

Note: You will also have to adjust the TDI port on all connectedwindream workstations (in the windream alias settings via theserver selection e.g. on tab page Connections of the windreamconfiguration).

4-10 Invisible domains or users/groups of domains

Invisible domains or users/groups of domainsIf either specific domains or users and groups of domains are notdisplaed correctly in the windream Management Console (folderwindream Administration>Users and groups >Network neighborhood) or if anadjustment does not lead to the desired result, this may have thefollowing reasons:

1. The account for the windream mainuser has not been created onthe Domain Controller(s) or the password is incorrect.

Solution:The user account of the windream mainuser must be created with thesame password on all Domain Controllers.

2. The windream mainuser has not been equipped with the requiredrights on the Domain Controller(s) to read off Domain, user orgroup information.

Solution:The windream mainuser must be assigned to Domain Controllers ofgroup "\Builtin\Pre-Windows 2000 compatibleAccess".

3. The protocol for "NetBIOS via TCP/IP" has been disabled on thewindream Server.

Solution: 1. In the network connections (Network neighborhood>Properties),highlight the entry for the LAN-connection. The specific LAN-connection must be selected that is responsible for thecommunication of the Domain Controllers.

2. Open the properties of the LAN-connection. 3. Select entry Internet protocol (TCP/IP) and open theproperties.

Open the advanced properties and enable the option of NetBios viaTCP/IP on tab page WINS.

Changing the user ID (name / password) of the windream mainuser 4-11

Changing the user ID (name / password) of the windreammainuser

If you want to change the user ID for the windream mainuser (assignnew password and/or new name), proceed as follows:

• Close windream Services and windream Control Center.• Change user ID on all Windows Servers, on which the windream

mainuser account has been configured. If you also want to changethe login name, please consider that there is no user yet existingunder the new ID in the windream user and group administration(see also chapter "How to change the user ID (Name and Password)for the windream database user", page 4-15 ff).

• Assign operating system rights for the windream mainuser on thewindream Server.

• Adjust DCOM settings and service settings usingWMStpCfg.exe.

• Adjust user ID for executing task Archiving anddeleting windream Objects.

• Change user ID of the windream database user with theadministration functions of the database used.

• Change ID for the windream mainuser in windream via fileWMShdw.exe.

• Start windream Control Center and windream Services.

Close windream services and Control Center 1. Close the windream Services (Thumbnail Service, Agent, Fulltext-Service, TCP-Service, DMS-Service and Objectstore-Service) viawindream Service Manager from the windream Control Center.After that, close the windream Control Center (from the taskbar).

Change user ID on operating system level 2. Change the user ID with the functions of the operating system'suser and group administration on all Servers on which themainuser account has been created; or create a new user account.These changes must be executed on one or several computers,depending on the current system architecture (PDC, windreamServer, Servers in other domainsanderen domains).

If you have created a new user account for the windream mainuser,several operating system rights must be assigned to the user on thewindream Server using the Windows users and group administration.

If you use program WMStpCfg.exe for configuring the DCOM andservices settings (see item 4), these settings will be made automatically.But check the settings in any case. Item 3 describes this procedure.

4-12 Changing the user ID (name / password) of the windream mainuser

Assign operating system rights for windream mainuser 3. The user must be member of the local administrator group

(assignment executed using the functions of the Windows user andgroup administration). Further on, the following operating systemrights must be assigned to the mainuser on the windream Server:

a. Act as part of the operating system b. Log on as service c. Log on as batch processing job.

Under Windows 2000 or higher, the assignment of operating systemrights (items a to c) is executed via the user rights command of thedirectives in the Windows user and group administration (user managerfor domains). In the dialog box of the directives for user rights, youenable the checkmark of further user rights. From the list of rights, youselect the desired entry. If the mainuser entry is not in the list, you willhave to add it.

Under Windows 2000 / 2003, the assignment of operating systemrights (items a to c) is executed over command Administration>Localsecurity directive from the Start menu. In the local security settings, youopen the folder for assigning user rights (over local directives). Markthe desired right und select command for security settings. If themainuser entry is not in the list, you will have to add it. See also"Operating system rights for windream mainuser " in chapter 2.

Adjust DCOM and service settings 4. For adjusting the DCOM and the service settings, call programWMStpCfg.exe from the windream program directory.

In the group named windream Main User, you enter the new user data forthe windream-Hauptbenutzer.

Note: Please urgently ensure that the user group is entered inwindream All Users Group that you originally have determined in theSetup as group of all windream users (the pre-setting is alwayswindream-user). In the windream Management Console, thegroup of all windream users is marked with an "X" in node users andgroups >windream>All groups in column All users.

Save the changes.

In case the windream mainuser account should have been created onthe target system already, a check of the password determined here willbe executed. If this check fails, if the determined user-ID does not exist


or if the passowrd entered is incorrect, the respective messages will beedited and you can correct the entries.

The required configurations for the windream services will be madeautomatically in the DCOM and service settings with the entries madehere. However, check the settings. A description of the steps can befound under item 5 and 6.

5. In the DCOM configuration, check the configuration changed forthe windream DMS Service and for the Thumbnail Service (useraccount under which DMS Service is executed). Thus, start theDCOM configuration (command Start>Run>dcomcnfg). Fromthe list of applications, select entry windream DMS-Service. Open the Properties and switch to tab page Identity.check the changed user data and adjust them if necessary.Additionally, if the name of the mainuser has been changed, checkwhether the new mainuser is entered in the list of accesspermissions (besides the entry in the windream user group); (tabpage Security – user-defined access permissions). Repeat this check for thewindream Thumbnail Service. See also "DCOM configuration forwindream DMS Service" in chapter 2.

6. Check the user ID for the windream Services in the servicessettings (command Start>Programs>Administration>Services). Thechanged user account must be entered in the Properties, underwhich the services are started (Logon tab page). This is valid forthe following services:

• windream Thumbnail Service,• windream Agent,• windream DMS Service• windream Fulltext Service.

Change user ID for windream task 7. Adjust the user ID, under which task Archiving andDeleting windream Objects is executed. Thus, openthe Scheduled Tasks folder from the control panel. Mark thewindream task and open the Properties. Determine the newpassword on the Task tab page in group Execute as. If you changename and password, you will also have to enter the new user name.Please consider that the designator of the domain or the Server onwhich the mainuser account has been created must also be entered:(<MYDOMAIN>\username or Servername\username).


Change user ID for windream database user 8. Change the user ID of the windream database user with the

administration functions of the database used (from SQL ServerEnterprise Manager or Oracle DBA Studio / Oracle EnterpriseManager). Depending on whether you only want to change thepassword or the name and the password of the user, differentactions are required (see also "How to change the password for thewindream database user", page 4-15 and "How to change the userID (name and password) for the windream database user", page 4-15).

Change user ID for windream mainuser in windream(WMShdw.exe)

9. Call file WMShdw.exe from the windream program menu(command Advanced>Password-File-Check-Change). First, theoriginally determined data of the windream mainuser has to beentered on the left side of the dialog box (name/password), thename is preset by the program. Via the Check command button,the entries are checked, and if the entry was correct, the inputfields for the new entries will be enabled. After having entered thenew name of a user (respectively his new password only), amessage box will be displayed whose notes are URGENTLY to beconsidered.

Note: Implicitly, the determined user will be authorized here to usethe windream ObjectStore Service, if this Service has been installedlocally.Otherwise, the access permission for the changed windreammainuser must be entered manually. Thus, you have to remove theexisting permission of the mainuser first, and you must assign itagain with the changed entriesafterwards. In directory windreamobjectstore\bin, you delete the authentication in an MSDOS box using command mmpasswd -del<mainuser_old> <Password_old>. Then, you assign thepermission via command mmpasswd -add<mainuser_new> <Password_new>. A note concerningthe syntax of command mmpasswd can be received by enteringmmpasswd –help (see also notes in chapter 1, "Installingwindream ObjectStore").

Starting the windream Control Center and the windream services 10. Start the windream Control Center (command

Start>Programs>windream>Control Center). Then, you start thewindream Services (Thumbnail, Agent, Fulltext-Service, TCP-Service, DMS-Service and – if required - Objectstore-Service) byexecuting file startservices.bat, via the windream Service


Manager or from Administration>Services. If services cannot bestarted, you will find a possible reason for the error in theWindows event log (in case of a message with incorrect logon,check name and password of the mainuser as described under item5 and 6). Here, incorrect entries are possible, as especially thepassword in the Windows dialogs will not be checked.

How to change the password for the windream databaseuserFor SQL Server, the change of the user ID is executed over therespective functions of Microsoft enterprise Manager, for Oracle fromthe DBA Studio or Enterprise Manager.

MS SQL Server: 1. In SQL Server Enterprise Manager, you switch to folder Consoleroot>Microsoft SQL Server>SQL Server-Group><windream DB-Server>.

2. Open folder Security>User name. 3. Mark the entry for the windream mainuser and open the

Properties. 4. On the General tab page, you enter the new password (field

Password) and confirm with OK. 5. Confirm the new password and save the changes.

Oracle: 1. Start Oracle DBA Studio / Enterprise Manager and select thewindream database.

2. Open folder Security>User (Oracle 8i: User names). 3. Select the entry for the windream mainuser. 4. Enter the new password on the General tab page in the group for

the permission control (fields for entering the password andconfirmation) and click the Apply button.

How to change the user ID (name and password) for thewindream database userMS SQL Server:If you have changed the password of the mainuser, you will have toproceed as follows in order to change the windream database user.

The basic requirement for a change is that the new windream databseuser is not yet a windream user, meaning that he does not exist yet asuser in the windream user and group administration of the windreamManagement Console. (If he already exists there, the followingprocedure may NOT be applied).


First, you will have to create a new user account in the database withthe desired ID (using the functions from MS SQL EnterpriseManager). Then, you must enter him as owner of the windreamdatabase (calling procedure sp_changedbowner via SQL ServerQuery Analyzer, see below). Ensure that no right for access to thewindream database is assigned here during the creating process. Afterhaving changed the database user, you will still have to adjust entries intable UserInfo. You can delete the original windream database userfrom the database at the end of the procedure.

If the domain has chnaged in which the mainuser has been registeredyou will also have to adjust the entry HKLM/Software/A.I.S.GmbH/windream/<windream version>/ConnectionAccountDomain= <Domain name>in the Windows Registry.We will now list the steps necessary for changing the windreamdatabase user:

1. In MS Enterprise Manager, switch to folder Console Root>MicrosoftSQL Server>SQL Server-Group><windream DB-Server>.

2. Open folder Security>User names. 3. Select command New User name from the context menu. 4. Enter the new name on the General tab page. 5. Select option SQL Server Authentication and enter the new password. 6. In area Default, you select the database (windream) and the

language. 7. Confirm with OK. 8. Confirm the new password and save the changes (if necessary,

confirm error message with Yes). 9. Start the Query Analyzer (command Programs>Microsoft SQL

Server>Query Analyzer) and log on to SQL Server under an SQLServer Admin-Login (for example with ID "sa"). (When enteringname and password, an explicitly available user of SQL ServerEnterprise Manager (f.ex. "sa") is to be determined. If user "sa"does not exist, a new user, f. ex. "Administrator",has to be createdwith the Server role Administrators.)

10. Select the windream database (entry windream in dropdownlistbox).

11. In the dialog, enter the following command:

exec sp_changedbowner 'NewMainuserName'

and execute this query. 12. Mark the entry of the original windream mainuser. 13. Delete the user from the database (command Delete from the

context menu). 14. Open folder Databases>windream>Tables. 15. Select entry UserInfo.

Enhancing the SQL Server database performance via the Named Pipes protocol 4-17

16. Select command Open table>Return all lines from the context menu. 17. Change the entry for the user name in column szUserName in

the line for the windream mainuser. If the domain has changed,too, you will also have to adjust the entry in columnszNTDomain respectively.

Note: After having finished the changes in SQL Server, you willstill have to call file WMShdw.exe to change the user ID fromwindream mainuser to windream (see item 8 under "Change userID of the windream mainuser", page 4-14).

If the domain has changed in which the mainuser is registered, youwill have to enter it underHKEY_LOCAL_Machine/Software/A.I.S.GmbH/windream/<windream version>/Connectionin the Windows Registry (AccountDomain =<DomainNew>).

Oracle 8i / 9i / 10i:When using Oracle, urgently ensure that the existing windreamdatabase scheme for the new windream database user will be appliedidentically. Ensure that the required rights the mainuser has receivedduring the Setup and the default tablespaces are correct. The Oraclecommands executed for this during the Setup can be found in thewindream application directory in subfolder DB, filescr_role_user.log and cr_grant_ctx.log.

Enhancing the SQL Server database performance via theNamed Pipes protocol

The performance of windream installations (especially version 3.5 andhigher) which use an SQL Server database running on a separate servercan be improved by switching to the Named Pipes protocol for thecommunication between DMS-Service and SQL Server. To achievethis, an alias must be created on the windream Server using the SQLServer Client configuration program with the following parameters:

Server alias: Name of the server on which the SQL Server operates;

Network library: Named Pipes;

Server name: Name of the server on which the SQL Server operates;

Pipe name: assigned automatically.

4-18 Enhancing the SQL Server database performance via the Named Pipes protocol

A requirement for the use of the Named Pipes protocol is that thewindream mainuser exists with the same password on the Server onwhich the SQL Server operates.

winwinwinwindreamServer UpdateServer UpdateServer UpdateServer Update

InstallationInstallationInstallationInstallation

5

Basic requirements for an update installation 5-1

windream Server ServicesUpdate InstallationBasic requirements for an update installation

The present description of an update installation serves as a help duringthe update process of the windream server services version 3.0 orhigher.

An update installation to version 3.5.x (or higher) of the windreamserver services is only possible from windream server version 3.0.

Notes on migration from windream 3.0 towindream 3.5 or 3.6

Note: During an update installation of the windreamserver services from 3.0.x to 3.5.x or 3.6x (migration fromwindream 3.0 to windream 3.5 or 3.6), the database scheme will beupdated and data already acquired in the database will be refreshed.This process will be executed by the setup automatically and maytake some time (windream will display a respective informationtelling you that the database is updated). The rollback space and thedata area of the database must be big enough to enable the systemto execute these transactions which refer to the complete dataamount of the documents (further technical details can be found inthe documentation of the database used).

Please backup your complete database before starting the updateprocedure. The description of a backup is not part of thisdescription. Thus, cf. the respective documentations of the databaseused.

Further requirementsThe following requirements must be fulfilled before an updateinstallation is executed:

• windream Control Center must be closed.• windream Services must be closed and startup of the services must

be changed from Automatical to Manual. These settings aremade automatically by setup during the update.

5-2 Basic requirements for an update installation

• If necessary, close a window of the Windows Control Panel(Start>Settings>Control Panel). Additionally, the Control Panel foldermay not be selected when Explorer windows are open.

Reason:

This would load windream libraries, and thus, the server must berestarted after an update. After the restart, additional settings andchecks would become necessary.

• ExecuteWMReg.bat file• Check DCOM and Services settings.• Set startup of windream services to automatical.• Start windream Services.

If the server need not be started, the necessary settings will be made bysetup, the services will be started again after the update. No otherconfigurations will be necessary.

If libraries or other processes are still active, a respective note willindicate that setup is cancelled. The processes displayed are to beclosed then, and setup has to be restarted.

Closing the windream servicesIn case you should have to close the services manually and switch thestartup type for the windream Services from Automatical toManual, we now describe how to make these settings. Otherwiseyou can proceed with chapter "Execute windream server Update", p. 5-4.

In order to close the windream services and to change the startup type,you call the dialog box Services with the commandStart>Programs>Administrative Tools>Services. The respective serviceswith their status and the startup type are displayed in a list. The servicesare to be terminated step by step in the following order:

• windream Thumbnail service• windream full-text service• windream TCP service• windream DMS Service• windream Event Service• windream Agent• windream ObjectStore Service (if installed).

Note: The services can also be closed via the Serviece Manager fromthe windream Control Center or via batchfile

Basic requirements for an update installation 5-3

stopservices.bat. The file will be installed during awindream installation in the resourcekit subdirectory of thewindream program directory.

How to close one of the windream servicesClosing thewindream services

1. Execute file stopservices.bat in the program directory ofthe windream server to close the services automatically.

Or

1. Open the windream service manager via the respective commandfrom the context menu of the windream Control Center.

2. Select the entry for all windream services in the list of services. 3. Click Close. 4. Close the service manager.

Or

1. Select the entry of the service to be terminated in the dialog boxServices.

2. Click Close in the title bar or select the respective command fromthe pop-up menu to close the service.

After that, the startup type setting Automatic has to be reset toManual for all windream services.

How to change the startup type of the windream servicesChange startup typeof the windreamservices

1. Select the entry of the service to be changed in the dialog boxServices.

2. Open the properties via the pop-up menu or via the icon of thetitle bar.

3. Enable the option Manual in the group startup type. 4. Click OK to apply the settings and to close the dialog box.

5-4 Updating the windream server

Figure 5-1: Changing the startup type of the windream services

Updating the windream serverThe update of the windream server setup is launched from theinstallation CD (setup.exe).

Starting the setup programStart the setup from the CD and follow the instructions.

Security question before executing the setupprogramIf the setup is started on an exisiting installation, a security question isdisplayed asking whether an update of the installed version or a newinstallation for example of single components (Service, database) shallbe executed. For an update installation, confirm with Yes(recommended).

If some components shall be post-installed or newly installed (like forexample a windream database which has not been installed yet), youwill have to click No. In this case, a completely new installation ofselected windream components is executed (see chapter 1, "Installwindream server (Launch setup)").

Selecting componentsGenerally, all windream components have to be selected for an updatewhich are installed on the respective server.

Updating the windream server 5-5

Figure 5-2: Update installation of the windream server – selecting components

Installing the databaseHere, you determine whether the setup program shall update thewindream database automatically or whether it shall only run therequired installation routines with the procedures for manual databaseadjustment.

Figure 5-3: Update installation of the windream server – installing the windream database


Install database Click this option if the required procedures shall be run by the setupprogram for updating the windream database. This is the defaultsetting.

Databse actions logonly

Select this option if the required procedures for updating the windreamdatabase shall be run manually instead of the setup program. The setupprogram will then create the required directories in the windreamprogram directory (\windream\DB\) and the installation routines. Itwill also install the required files and logs the steps to be executedmanually in file DB\Database_Actions_<timestamp>.log.

windream database typeHere, you determine the database type if you want to update thewindream server components without the database components only.

Figure 5-4: Update installation of the windream server – select database type

windream licensingThe license data can be checked and – if required - a new license keycan be entered in the respective dialog box. The update installation ofthe windream server from version 3.6 to 4.0 requires the entry of a newlicense key (see also chapter 1, "Licensing").

Note: Over the button From File, you can open and read-in the filewith the modified licensing data which you received from yourpartner (default: WMCustom.ini). This is recommended to avoiderrors which might occur when data are entered manually.


Updating the windream database / databasefulltext extensionThe user ID of the windream mainuser (name and password) isrequired for an update of the windream database components and thefulltext extension. This is necessary to get access to the database.During the update installation, the Stored Procedures and the tables arechanged.

Depending on the database used (SQL server or Oracle), differentdialog boxes are displayed for entering the database data. Except theentry of the SQL DB server name or the Oracle Net8 service name, theentries are identical.

MS SQL server

Figure 5-5: Update installation of the windream-server – windream database (SQL server)


Oracle

Figure 5-6: Update installation of the windream-server – windream database (Oracle)

The server name with which the windream database has been installed(respectively Oracle Net8 service name) and the name of the databaseto be updated are displayed. The displayed database ID is notconsidered during an update and id thus inactive.

If the database components are not updated, this dialog box will alsobe displayed. However, only data of the windream mainuser will beevaluated then (fields Mainuser, Password and confirmation).

Note: In case the windream mainuser determined here shouldalready be available on the target system, the password determinedwill be checked. Respective messages will be displayed, if this checkfails, if the determined user-ID does not exist or if the passwordentered is wrong. The setup program will not be cancelled. You willget the opportunity to correct the entries before the setup programis continued. In any case, please ensure that the user-ID and thepassword entered are correct.

For the windream Services which do not operate under the localsystem account, those user accounts will be entered again whichhad also been determined originally. If the mainuser accountdetermined during the update installation is different from thatwhich has been determined for the Fulltext Service, the DMS-Service, the Agent, the Event Service and the Thumbnail Service, adialog will be displayed at the end of the server setup routine forevery service, in which you enter the user-ID under which therespective service shall be run.


Oracle database settings updateThis dialog box will onyl occur, if windream is used with Oracle.Otherwise, you can proceed with topic "SQL server Authentication".

Figure 5-7: Oracle database settings

Index tablespace Here, you enter the names for the Index Tablespace. By default, thename is preset with USERS. During an update installation, only newindices will be created in this tablespace. The tablespaces determinedhere must have been created before the installation of the windreamdatabase (see also chapter "Oracle database settings " in chapter 1).

Oracle CTXSYS login - updateHere, you enter the user login for the Oracle CTXSYS-user. This dialogbox will only occur if windream is used with Oracle. Otherwise,proceed with topic "SQL server Authentication".


Figure 5-8: Update - windream-Oracle CTXSYS login

Enter the Oracle CTXSYS user name here (default: ctxsys) and thepassword (see also chapter "Oracle CTXSYS Login - Update" inchapter 1).

SQL server authenticationHere, you select the type of authentication for MS SQL server in orderto install and configure the windream database. If you use Oracle, youcan proceed with chapter "Oracle Authentication".

Please cf. the notes in chapter "MS SQL server Authentication“ ofchapter 1.


Figure 5-9: Installation of windream-server – SQL server authentication

Note: In order to check the user data entered, setup will try a loginto the previously determined database with the entered user ID forauthentication. Additionally, the system will check whether a loginto the database is possible with the user ID entered for thewindream mainuser. Respective messages will be displayed in caseof errors. In order to solve problems, you can correct the entries inthe respective dialog boxes (windream Database Refresh and SQL serverAuthentication). setup can also be continued without changes at thispoint. In this case, you will be informed that the databaseinstallation cannot be executed correctly, as a login to the databaseis not possible.

Windows NTauthentication

Select this option, if the currently logged-in user is member of the SQLserver administrator group and if the NT authentication shall be usedas MS SQL server Administrator Login. Generally, the setting namedWindows NT Authentication is correct (default).

SQL serverauthentication

Enable this option, if SQL server Authentication shall be used as MSSQL server Administrator Login. In the fields Name, Password andPassword confirmation you enter the user ID of the user accountpreviously created in SQL Enterprise Manager (see also chapter "MSSQL server Authentication" in chapter 1).

Oracle authenticationAt this point, you enter the data for the authentication in order toinstall and configure the windream database.


Please also consider the notes under topic "Oracle Authentication" ofthe first chapter.

Figure 5-10: Installation of the windream server – Oracle-Authentication

Note: In order to check the user data entered, setup will try a loginto the previously determined database with the entered user ID forauthentication. Additionally, the system will check whether a loginto the database is possible with the user ID entered for thewindream mainuser. Respective messages will be displayed in caseof errors. In order to solve problems, you can correct the entries inthe respective dialog boxes (windream Database Refresh and OracleAuthentication). setup can also be continued without changes at thispoint. In this case, you will be informed that the databaseinstallation cannot be executed correctly, as a login to the databaseis not possible.

Explicitauthentication

Oracle only supports this option. An NT authentication is notsupported by Oracle. In the Fields named DBA Name, Password andPassword Confirmation you enter the data of the Oracle DBS login tobe used (see also topic "Oracle Authentication" in the first chapter).

Start copying processAfter that, you start the copying process in the respective dialog box toupdate the windream server.

Updating the windream main services and the windream fulltext service 5-13

Setting the start type of the windream servicesand starting the servicesIn order to reset the start type of the windream services to the originalstatus again, you confirm the respective message with Yes.

Then, you can start the windream services by confirming the respectivemessage with Yes.

Update completeAfter having completed the update installation, you can display thelogfiles for reading diagnostic outputs and the readme file.

Figure 5-11: Installation of windream server – setup complete

Generally, it is not necessary to reboot the system.

Updating the windream main services and the windreamfulltext service

The steps, settings and checks are listed now, which are to be executedafter a successful update installation of the windream main services andthe fulltext service.

Note: These settings and checks need only be executed manually,if a reboot of the system had become necessary after the updateinstallation. Otherwise, the configurations needed are made by the

5-14 Updating the windream main services and the windream fulltext service

setup, and the windream services will be started again after havingfinished the update installation.

• Execute the WMReg.bat file.• The required DCOM- and service settings can then be made with

the WMStpCfg.exe file in the windream program directory.• Check DCOM configuration for the windream DMS Service.• Check settings in Administrative Tools>Services for the windream DMS

Service.• Start windream services (Administrative Tools>Services).• If necessary, set startup type of the windream services onAutomatic.

• Check whether the update of the windream database componentswas executed successfully (WMInitUpdateDB.log respectively\<timestamp> upd_db.log).

ExecuteWMReg.bat

First, the WMReg.bat file which is created in the windream programdirectory (<windream Program Directory>) has to beexecuted manually after an update installation and the reboot of thesystem.

Adjusting theDCOM- andservice settings

In order to adjust the DCOM and the service settings, you startWMStpCfg.exe from the windream program directory. Therequired configurations will be executed automatically for the serviceswith the user and group data entered here for the windream mainuserand for the windream user groups. Please note that the correctpassword of the windream mainuser and the correct user and groupnames are entered here.

After that, you still have to execute the following checks and settings.

Check DCOMconfiguration forthe windream DMSService

Open the DCOM configurations for checking the windream DMSservice. Then, close the DCOM configurations by clicking OK. After anupdate installation, you will have to make the settings here just likeafter a new installation (see also chapter 2, "DCOM configuration forwindream DMS Service").

Check settings inAdministrativeTools> Services forwindream DMSService

After that, you check the settings for the windream DMS service inStart>Programs>Administrative Tools>Services. Especially the windreammainuser must be entered in the group login as when the startup type isconfigured. After an update installation, the settings must be made hereexactly like after a new installation. (see also chapter 2, "Adjustments inthe Administration – Services").

Start windreamservices

After that, the windream services are to be started again. For startingthe service and changing the startup (if necessary), call the dialog boxServices with the command Start>Programs>Administrative Tools>Services(see also chapter 2, "Adjustments in the Administration – Services").The windream services must be started one after the other in the

Updating the windream main services and the windream fulltext service 5-15

following order:

• windream ObjectStore Service• windream DMS Service• windream Agent• windream TCP Service• windream Fulltext Service• windream Thumbnail Service• windream Event Service.

Note: The services can also be started via the Service Manager fromthe windream Control Center or via batchfilestartservices.bat. The file will be installed in thewindream program directory during the installation (see alsochapter 2, "Settings in the administration – services").

The windream Event-Service will not be started automaticallyduring a new installation or after an update from windream 3.x to4.0. An update from windream 4.x to 4.y will start the event serviceautomatically again, if the start type has been defined asAutomatical.

Change startup typeof windream services

If necessary, the setting of the startup for the respective windreamservices has to be switched to Automatic (see also chapter 2,"Adjustments in the Administration – Services").

Check update ofwindream databasecomponents

For checking whether the update installation of the windream databaseand the windream database fulltext extension has been successful, youopen the logfile DB\WMInitUpdateDB.log (respectivelyDB\<timestamp>\upd_db.log), which has been saved in theprogram directory of windream. This file represents a protocol on thesuccessful update process. If the update was not successful, you willfind the necessary information there.

5-16 List of update logfiles and diagnostic outputs

List of update logfiles and diagnostic outputsFile Name Created by<WINDOWS> \WMInst.log

windream server installation

<windream>\DB\<timestamp>_WMInitUpdateDB.log

windream server update /windream log for SQL serverupdate Init-DB functions.

<windream>\DB\<timestamp>_upd_db.log

windream server update /windream log for Oracle DBUpdate.

Table 5-1: windream server update logfiles and diagnostic outputs

Annotations

6

Table of Figures 6-1

Table of FiguresFigure 1-1: SQL Server Properties 1-8Figure 1-2: SQL Server Service Manager 1-9Figure 1-3: Identification of the connected Windows 2000 workstations 1-16Figure 1-4: Identification of the connected Windows 2000 workstations (standalone

server) 1-17Figure 1-5: Identification change of the connected Windows 2000 workstations

(standalone server) 1-18Figure 1-6: SQL Server properties – security 1-19Figure 1-7: SQL Server Authentication 1-20Figure 1-8: SQL Server login properties – new user 1-21Figure 1-9: Choose Type of setup 1-23Figure 1-10: Select Components 1-24Figure 1-11: Selecting the database type 1-26Figure 12: Installation of the windream server – installing the windream database 1-27Figure 13: Installation of the windream server - windream authentication 1-28Figure 1-14: Licence information 1-29Figure 1-15: TDI-Settings 1-30Figure 1-16: Enter ObjectStore data 1-31Figure 1-17: Configuration of file storage directory 1-33Figure 1-18: Determination temporary directory 1-34Figure 1-19: Entering database information for SQL Server 1-35Figure 1-20: Entering database information for Oracle 1-36Figure 1-21: Installation of the windream-Server – Oracle Database Settings 1-38Figure 1-22: windream-Oracle CTXSYS login 1-40Figure 1-23: windream user / group configuration 1-41Figure 1-24: SQL Server authentication 1-45Figure 1-25: Oracle authentication 1-46Figure 1-26: Start Copying Process 1-47Figure 1-27: Starting the windream services 1-47Figure 1-28: Setup complete 1-48Figure 2-1: Properties of the windream DMS Service– Tab Page General 2-5Figure 2-2: Properties of the windream DMS Service – Tab Page Location 2-6Figure 2-3: Properties of the windream DMS Service – tab page Security 2-7Figure 2-4: Configuring launch permission for users and groups 2-8Figure 2-5: Changing access permissions for users and groups 2-9Figure 2-6: Configuring the access permission 2-10Figure 2-7: Configuring the configuration permissions for users and groups 2-11Figure 2-8: Properties of the windream DMS Service – Tab Page Identity 2-12Figure 2-9: Starting the windream Services 2-15Figure 2-10: Configure Services – windream DMS Service 2-16Figure 2-11: windream Configuration 2-19Figure 2-12: SQL Server Enterprise Manager 2-26Figure 2-13: SQL Server Enterprise Manager – Folder Fulltext Catalog 2-26Figure 2-14: Schedules for Fulltext Indexing 2-27Figure 2-15: Create New Schedule for Fulltext Population 2-27Figure 2-16: Create New Schedule for Repeated Fulltext Population 2-28

6-2 Table of Figures

7

Figure 2-17: Schedules for Fulltext Indexing. 2-29Abbildung 2-18: Assigning windream rights to root directory 2-33Figure 3-1: Closing the windream services 3-4Figure 3-2: windream Server Uninstallation – Delete windream Database 3-5Figure 3-3: Uninstall windream Server – Delete windream Database User 3-5Figure 5-1: Changing the startup type of the windream services 5-4Figure 5-2: Update installation of the windream server – selecting components 5-5Figure 5-3: Update installation of the windream server – installing the windream

database 5-5Figure 5-4: Update installation of the windream server – select database type 5-6Figure 5-5: Update installation of the windream-server – windream database (SQL

server) 5-7Figure 5-6: Update installation of the windream-server – windream database (Oracle)

5-8Figure 5-7: Oracle database settings 5-9Figure 5-8: Update - windream-Oracle CTXSYS login 5-10Figure 5-9: Installation of windream-server – SQL server authentication 5-11Figure 5-10: Installation of the windream server – Oracle-Authentication 5-12Figure 5-11: Installation of windream server – setup complete 5-13

Table of Charts 6-3

Table of ChartsTable 1-1: Number of MS-DOS windows during installation 1-48Table 1-2: windream Server Logfiles: windream Installation 1-51Table 1-3: windream Server Logfiles: windream and MS SQL Server 1-52Table 1-4: windream Server Logfiles: windream and Oracle 1-53Table 1-5: windream Server Logfiles: while operating windream 1-53Table 1-6: windream Server Logfiles: general outputs 1-53Table 5-1: windream server update logfiles and diagnostic outputs 5-16

Index 6-5

Index

AAccess Administration

Determine 2-23Access Permission

windream ObjectStore 1-10Access Rights

DCOM Configuration 2-6windream DMS Service 2-6

Access to windream Services denied4-1

Adjustmentswindream Configuration 2-17

Assignwindream Rights for Root

Directory 2-32

BBasic Settings

windream Server 2-1Basics

Installation 1-2windream Server Installation 1-2

CChange

Group Assignments of Users 4-2User ID of mainuser 4-11

CheckInstallation 1-49Schedule Fulltext Population 2-22Update Installation 5-13windream setup Logfiles 1-50

Check License Data 2-22Choose Components

setup 1-24windream Server setup 1-24

Client-Server Systems Architecture 1-3

Closewindream Services 3-3

Completeserver setup 5-13setup 1-47windream Server setup 1-47

Componentswindream Database 1-24, 5-4windream Database Fulltext

Extension 1-24, 5-4windream Fulltext Service 1-24, 5-4windream Main Services 1-24, 5-4

windream System Libraries 1-24, 5-4

ConfigurationObjectStore Service 2-20Schedule Fulltext Population 2-22Tab Page License 2-22windream Server 2-1

Configuration RightsDCOM Configuration 2-6windream DMS Service 2-6

Configurewindream user 1-15windream Users 1-14

ConnectionsControl 2-20

Context menu unavailable 4-1Control

of Connections 2-20of File Filters 2-20

Control Panel Serviceswindream Services 2-14

Copying Processserver Update 5-12setup 1-46, 5-12Update 5-12windream Server setup 1-46

Copying Processserver setup 5-12

Createwindream Groups 1-12windream mainuser Account 1-14

DDatabase

Installation 1-38server Update 5-7Update 5-7

Database AdjustmentsDB ID 1-37

Database Connectionwindream Configuration 2-20

Database SettingsDB mainuser 1-37DB Name 1-37DB Server Name 1-36Net8 Service Name 1-36

Database type 5-6Database Type 1-25DB ID

Database Adjustments 1-37DB mainuser

Database Settings 1-37DB Name

Database Settings 1-37DB Server Name

Database Settings 1-36DCOM Configuration

Access Rights 2-6Configuration Rights 2-6

6-6 Index

Start Rights 2-6Tab Page Identity 2-11Tab Page Location 2-5tab page Security 2-6windream DMS Service 2-4

Deletewindream Database 3-1, 3-4windream Database User 3-1, 3-5

Destination Foldersetup 1-29windream Server setup 1-29

DetermineAccess Administration 2-23Global Script Directory 2-23

Display of logfilesWMShowLg.bat 1-49

DMS Service does not start 4-2Incorrect setting DCOM

configuration / Control Panelservices 4-4

ObjectStore Service not configuredor started 4-4

windream Database Name incorrect4-4

EError while creating

Database 4-6Database Users 4-6

Error while creating fulltextcomponents 4-6

Error while executing WMInit.exe 4-2Error while initial filling

Database 4-6

FFile Filter

windream Configuration 2-20File Filters

Control 2-20Finished

server Update 5-13setup 5-13Update 5-13

Fulltext PopulationSchedule 2-25

GGlobal Script Directory

Determine 2-23Group Assignments of Users

Change 4-2Groups See windream Groups

HHard Disk Capacity

System Requirements 1-9

IIncorrect setting DCOM

configuration / Control Panelservices

DMS Service does not start 4-4windream DMS Service does not

start 4-4Incorrect windream Database name

DMS Service does not start 4-4Incorrect windream Mainuser


start 4-2Index Tabelspace

Oracle database settings 5-9Index Update

Background 2-30Information


Installwindream Server 1-22

InstallationBasics 1-2Check 1-49Show logfiles 1-48

Installation windream ServerRequirements 1-3, 1-11System Requirements 1-3windream ObjectStore 1-10

LLanguage Version

Setup 1-22windream Server setup 1-22

Licence Indicationssetup 1-28

Licensewindream server Update 5-6

License DataCheck 2-22

License EntriesUpdate 5-6

Licensingwindream Server setup 1-28

Logfiles 1-48Server setup 1-51

MMainuser

Change ID 4-11

Index 6-7

Change Password 4-11MS SQL server Authentication 5-10

SQL-server Authentication 5-10Windows NT Authentication 5-10

MS SQL Server Authentication 1-20,1-44

SQL Server Authentication 1-20, 1-44

Windows NT Authentication 1-20,1-44

NNet8 Service Name

Database Settings 1-36

OObjectStore Service

Uninstall 3-1windream Configuration 2-20

ObjectStore Service not configured orstarted


start 4-4ObjectStore Settings

Port 1-31Server 1-31

Oracle Authentication 1-21, 1-45, 5-11

server setup 5-11Server setup 1-45

Oracle databaseIndex Tabelspace 5-9

Oracle Database SettingsTemp Tabelspace 1-39User Tablespace 1-39

Oracle Jobs for Fulltext Indexing 2-31osql.exe 1-38

PPassword, change

Mainuser 4-11Port

ObjectStore Settings 1-31Program Folder


RRequirements

Installation windream Server 1-3Installation windream Server 1-11

Right Log on as Servicewindream Mainuser 2-3

Rights for the Root DirectoryAssign 2-32

SSchedule

Fulltext Population 2-25Schedule Fulltext Population

Check 2-22windream Configuration 2-22

Scheduled Tasks 2-25Select Components

Server Update 5-4setup 5-4Update 5-4windream server setup 5-4

serverInstall Update 5-4Update Call 5-4

ServerObjectStore Settings 1-31Update Log Files 5-16

Server - Client Systems Architecture1-3

server setupComplete 5-13Copying Process 5-12Database type 5-6Oracle Authentication 5-11Select Components 5-4Start 5-4

Server setupAuthentiocation 1-27Database installation 1-26Logfiles 1-51Oracle Authentication 1-45

server UpdateCopying Process 5-12Finished 5-13Start 5-4windream Database 5-7

Server UpdateSelect Components 5-4

Settingswindream Server 2-1

setupChoose Components 1-24Complete 1-47Components 5-4Copying Process 1-46, 5-12Finished 5-13Information 1-23Language Version 1-22Licensing 1-28Select Destination Folder 1-29Select Program Folder 1-44Software Licence Contract 1-23SQL Server Authentication 1-44Start 1-23, 5-4System Libraries 1-26

6-8 Index

Type of setup 1-23User/Group configuration 1-40windream database 1-35windream ObjectStore 1-30windream TDI-Settings 1-29

setup callwindream Server 1-22

setup TypeStandard 1-23

Shut downwindream DMS Service 3-1windream Fulltext Service 3-1windream Fulltext-Service 3-4windream ObjectStore Service 3-1windream Services 3-1windream TCP Service 3-1

Software Licence Contractsetup 1-23windream Server setup 1-23

SQL ServerRemote Index Update 2-30

SQL server AuthenticationUpdate 5-10windream-server Update 5-10

SQL Server Authentication 1-20, 1-44setup 1-44windream Server setup 1-44

sqlplus.exe 1-38SQL-server Authentication 5-10Start

server setup 5-4server Update 5-4setup 1-23, 5-4Update 5-4windream DMS Service 2-14windream Fulltext Service 2-14windream ObjectStore Service 2-14windream Server setup 1-23windream Services 2-14windream TCP Service 2-14

Start RightsDCOM Configuration 2-6windream DMS Service 2-6

Startupwindream DMS Service 2-14windream Fulltext Service 2-14windream ObjectStore Service 2-14windream Services 2-14

Startup windream TCP Service 2-14System Adjustments

windream DMS Service 2-14windream Fulltext Service 2-14windream ObjectStore Service 2-14windream Services 2-14windream TCP Service 2-14

System Librariessetup 1-26windream Server setup 1-26

System RequirementsHard Disk Capacity 1-9Installation windream Server 1-3

windream Database 1-6windream Services 1-4

System Settingswindream Server 2-1

TTab Page Common

windream Configuration 2-23Tab Page Connections

windream Configuration 2-20Tab Page Filter

windream Configuration 2-20Tab Page Fulltext

windream Configuration 2-22Tab Page Identity

DCOM Configuration 2-11Tab Page License

windream configuration 2-22Tab Page Location

DCOM Configuration 2-5tab page Security

DCOM Configuration 2-6TCP-Service

No start 4-8Temp Tabelspace

Oracle Database Settings 1-39Typ of setup

windream Server setup 1-23Type of setup

setup 1-23User-defined 1-23

UUninstall

ObjectStore Service 3-1windream Server Services 3-1

Uninstall ObjectStore Sevice 3-1Uninstall windream Server Services 3-

1Update 5-4

Copying Process 5-12Database 5-7Finished 5-13License entries 5-6Select Components 5-4SQL server Authentication 5-10Start 5-4

Updatewindream server 5-4

Update InstallationCheck 5-13WMReg.bat 5-14

Update Log Fileswindream server 5-16

User authentications 1-27User ID of mainuser

Change 4-11User Tablespace

Index 6-9

Oracle Database Settings 1-39User/Group configuration


Users See windream Users

WWindows NT Authentication 1-20, 1-

44, 5-10windream Administrators

windream Groups 1-13windream Configuration

Adjustments 2-17Database Connection 2-20File Filter 2-20Tab Page Common 2-23Tab Page Connections 2-20Tab Page Filter 2-20Tab Page Fulltext 2-22

windream databasesetup 1-35windream Server setup 1-35

windream Database 1-24Delete 3-1, 3-4System Requirements 1-6

windream Database FulltextExtension 1-24

windream Database name incorrectwindream DMS Service does not

start 4-4windream Database User

Delete 3-1, 3-5windream DMS Service

Access Rights 2-6Configuration Rights 2-6DCOM Configuration 2-4Shut down 3-1Start 2-14Start Rights 2-6Startup 2-14System Adjustments 2-14windream Mainuser 2-11

windream DMS Service does not start4-2

Incorrect setting DCOMconfiguration / Control Panelservices 4-4

Incorrect windream Mainuser 4-2ObjectStore Service not configured

or started 4-4windream Database Name incorrect

4-4windream Fulltext

ServiceStartup 2-14

windream Fulltext Service 1-24Shut down 3-1, 3-4Start 2-14System Adjustments 2-14

windream GroupsCreate 1-12windream Administrators 1-13windream Users 1-13

windream Main Services 1-24windream mainuser

Right Log on as Service 2-3windream Mainuser

windream DMS Service 2-11windream mainuser Account

Create 1-14windream ObjectStore

Access Permission 1-10Installation windream Server 1-10setup 1-30windream Server setup 1-30

windream ObjectStore ServiceShut down 3-1Start 2-14Startup 2-14System Adjustments 2-14

windream ServerBasic Settings 2-1call setup 1-22Configuration 2-1Install 1-22Settings 2-1System Settings 2-1

windream Server InstallationBasics 1-2

windream Server ServicesUninstall 3-1

windream Server setupChoose Components 1-24Complete 1-47Information 1-23Language Version 1-22Licensing 1-28Select Destination Folder 1-29Select Program Folder 1-44Software Licence Contract 1-23SQL Server Authentication 1-44Standard 1-23Start 1-23Start Copying Process 1-46System Libraries 1-26Type of setup 1-23User/Group configuration 1-40User-defined 1-23windream database 1-35windream ObjectStore 1-30windream TDI-Settings 1-29

windream ServicesClose 3-3Control Panel Services 2-14Shut down 3-1Start 2-14Startup 2-14System Adjustments 2-14System Requirements 1-4

windream setup Logfiles

6-10 Index

Check 1-50windream TCP Service

Shut down 3-1Start 2-14Startup 2-14System Adjustments 2-14

windream TDI-Settingssetup 1-29windream Server setup 1-29

windream userConfigure 1-15

windream UsersConfigure 1-14windream Groups 1-13

windream-server UpdateLicense 5-6SQL server Authentication 5-10

WMCustom.ini 5-6WMReg.bat

Update Installation 5-14WMShowLg.bat 1-48

Display of logfiles 1-49

Server Installation - windreamdownload.windream.com/wd40/dokumente/serversetup-e.pdf · Basics of...

Documents

Transcript of Server Installation - windreamdownload.windream.com/wd40/dokumente/serversetup-e.pdf · Basics of...