saperion inter server installation 2007 - kofax · pdf file4.1 initial configuration ... 7...

SAPERION Inter Server Installation 2007

Copyright © 2016 Lexmark. All rights reserved.

Lexmark is a trademark of Lexmark International, Inc., registered in the U.S. and/or other countries. All other trademarksare the property of their respective owners. No part of this publication may be reproduced, stored, or transmitted in anyform without the prior written permission of Lexmark.

Table of Contents

1 System Requirements ......................................................................................... 1

1.1 Windows Server 2003 ......................................................................................... 1

1.2 Windows Server 2008 ......................................................................................... 1

1.3 SAPERION Requirements ................................................................................... 2

2 System Components ........................................................................................... 2

2.1 Configuration Server ........................................................................................... 2

2.2 SAPERION Inter Server ...................................................................................... 3

2.3 LogService ............................................................................................................ 3

2.4 SharePoint Extensions ........................................................................................ 3

2.5 Inter Server Gather .............................................................................................. 3

3 Inter Server Installation ...................................................................................... 3

3.1 Upgrade ............................................................................................................... 3

3.2 Installation Overview .......................................................................................... 4

3.2.1 Installing Configuration server and SAPERION Inter Server ........................ 4

4 Inter Server Configuration .................................................................................. 9

4.1 Initial Configuration ............................................................................................ 9

4.1.1 SQL Server Configuration ............................................................................... 10

4.1.2 Inter Server Configuration .............................................................................. 11

4.1.3 LogService Configuration ................................................................................ 11

4.1.4 Installed Programs .......................................................................................... 12

4.1.5 Folder Structure ............................................................................................... 12

4.1.6 System Services ............................................................................................... 13

4.2 Configuration ....................................................................................................... 13

4.2.1 Configuration Server Settings ......................................................................... 15

4.2.2 Pipelines Configuration ................................................................................... 17

4.2.3 Addins Configuration ...................................................................................... 18

4.2.4 Repository Configuration ................................................................................ 18

4.2.5 LogService ........................................................................................................ 20

5 Testing the Installation ....................................................................................... 21

5.1 Test the Server Functionality .............................................................................. 21

5.2 Test the Repository Configuration ...................................................................... 21

6 Installation of SAPERION Inter Server Gather .................................................. 23

7 Installation of SAPERION Inter Server Solution - MOSS 2007 ......................... 25

8 Starting Inter Server ............................................................................................ 27

9 License ................................................................................................................. 28

9.1 License Request ................................................................................................... 28

9.2 License Installation ............................................................................................. 28

10 Inter Server (Web View) ...................................................................................... 28

10.1 Retention Period .................................................................................................. 29

10.2 Security Settings .................................................................................................. 29

11 Appendix A. Installation Alternative ................................................................... 29

12 Appendix B. SQL-connection strings ................................................................. 29

13 Appendix C. Registry Entries .............................................................................. 29

13.1 General Settings .................................................................................................. 30

13.2 Mapping of Host Names ................................................................................... 30

13.3 Extended settings of TCP Connections .............................................................. 30

14 Appendix D. Hints for clustered / load-balanced installations ......................... 31

15 Appendix E. Used Ports ...................................................................................... 31

1.1 Windows Server 2003

1

SAPERION Inter Server Installation 2007

1 System Requirements

Inter Server runs on Windows Server 2003 and Windows Server 2008.

Also required are:

+ Microsoft .Net Framework 4.0 or higher

+ Microsoft SQL-Server

+ Silverlight


For Windows Server 2003, the following features must be activated (use Windows Component Wizard

to install them):

+ Microsoft IIS 6.0 or higher

+ MSMQ (Microsoft Message Queuing)

+ ASP.NET


For Windows Server 2008, the role Web Server (IIS) has to be installed. Make sure the following role

services are also installed:

+ Static Content

+ Default Document

+ Directory Browsing

+ HTTP Errors

+ ASP .NET

+ .NET Extensibility

+ ISAPI Extensions

+ ISAPI Filters

You also have to install and enable:

+ .NET Framework 4.0 Features

2 System Components

2

+ Message Queuing

1.3 SAPERION Requirements

Before installing Inter Server, make sure you have:

+ installed SAPERION ECM with Java core server

+ SAPERION Web Services available on Apache Tomcat

+ LDAP Synchronized User Management, if you are using ACLs

As well, a technical user must be set up in the SAPERION user management for the integration solution

(administrator rights are not a requirement).

i System properties such as SYSTIMESTAMP, SYSACLLIST, SYSROWID may need to be updated

in the repository definitions (i.e. the DDC) after installing Inter Server.

2 System Components

2.1 Configuration Server

The Configuration server is an ASPX-Application used to configure all SAPERION applications. The

applications communicate via web services with the Configuration server to download updates and

2.2 SAPERION Inter Server

3

to query their configuration. The application also allows upgrading of installed applications and

downloading of further options. Hence a centralized update distribution and configuration is possible.

2.2 SAPERION Inter Server

SAPERION Inter Server is a Windows service. The service is used to store documents to and retrieve

documents from the connected repositories and can additionally make them available to SharePoint

Gather.

2.3 LogService

The LogService is a Windows service and only needs to be installed once. The LogService audits all

events in a SQL-Table. The audit entries can be retrieved via the Configuration server. The applications

use MSMQ to communicate with the LogService.

2.4 SharePoint Extensions

The SharePoint extensions are used to adapt SharePoint functions for using the Inter Server archiving

and content integration features. There are solutions for SharePoint 2007 and SharePoint 2010.

2.5 Inter Server Gather

Install the Inter Server Gather (protocol handler) if you would like to index repositories for the MS Index

Technology.

3 Inter Server Installation

3.1 Upgrade

To upgrade from an earlier version, uninstall the old version first. All settings will remain the same.

If you used a version prior to 2.4.4, all changeable files will be migrated to the new paths based on

“%ALLUSERSPROFILE%\Saperion”. Following are the default paths:

+ Server 2008: C:\ProgramData\Saperion

+ Server 2003: C:\Documents and Settings\All Users\Application Data\Saperion


4

An automatic migration of settings and licenses will be executed on first start of the Inter Server after

reinstallation. As well, the services must be set to automatic if they are to start automatically.

3.2 Installation Overview

Inter Server installation is done in three steps:

+ Installation of the Configuration server and SAPERION Inter Server

+ Installation of the SAPERION Inter Server Gather

+ Installation of the SAPERION Inter Server Solution - MOSS 2007

i While all components can be installed on one computer (typically a web front-end server), it is

generally recommended to distribute the components on multiple servers. See the graphic below.

Fig. 3–1: Recommended server installation

Redistributable Setup

SAPERION Inter Server uses files from Visual C++ 2008, so you will need to install the Microsoft Visual

C++ 2008 Redistributable Setup first. The appropriate version for your system architecture (x86 or x64)

must be installed on all system components.

i You must use Visual C++ 2008 SP1 when using Windows Server 2008 R2.

3.2.1 Installing Configuration server and SAPERION Inter Server

1. Start the SAPERION Inter Server Setup program by double-clicking the "setup.cmd" file.

The SAPERION Configuration server opens in a browser window. All the necessary

components can be initialized in this window.


5

Fig. 3–2: Configuration server

2. Start Setup and select the components you would like to install.

+ Microsoft C++ 2008 Redistributable Setup

Must be installed on every machine. Select the version for the processor architecture

you are using.

+ ConfigServer and Inter Server

Must be installed once. A web site using port 1222 and a web site using port 89 will

be prepared.

+ Extensions and Gather for Office SharePoint Server

These components must be installed on a SharePoint server (farm).

Select “ConfigServer and Inter Server Manager” to install the basic functionality.

3. Click "ConfigServer and SAPERION Inter Server". A warning appears. Click [Run]. The

setup dialog opens. Click [Next].

4. Check the "I accept the license conditions" check box and click [Next].

5. Choose the type of installation you would like by clicking the corresponding button:

+ Typical

Installs the typical program options. This type of installation is recommended for

most users.

+ Custom

Allows you to select which program options should be installed as well as where they

should be installed. This type of installation is only recommended for advanced users.

+ Complete

All program options are installed. Therefore, this type of installation needs the most

disk space.

6. If you have more than one server to install, select Custom and choose the features you

want to install on this machine.


6

Fig. 3–3: Custom install

i Web sites must have an IIS installed on the same machine on which

they will be installed.

7. Enter the Service account to be used for Inter Server, Active Migration Manager and Active

Log service, with the corresponding password. This account needs access to the local

system, the databases and the backend storage.

Click [Next].


7

Fig. 3–4: Service account

8. Click [Install] to begin the installation.

Fig. 3–5: Install Inter Server

9. Click [Finish] to complete the installation.


8

Fig. 3–6: Finish installation

When you have finished the installation, you will see the menu entries available in the SAPERION group

in your Start menu.

4.1 Initial Configuration

9

Fig. 3–7: Start menu

4 Inter Server Configuration

During installation, a shortcut to the Configuration Server is added to the Windows Start Menu. By calling

the ConfigurationServer website, you are automatically in the application configuration window.


Before you install SAPERION Inter Server Gather and Inter Server Solution - MOSS 2007, you must

configure and test Inter Server so that it can run.


10

Fig. 4–1: ConfigurationServer Start Page

To begin the configuration of the initial settings, click Start > All Programs > SAPERION > ConfigServer

(WebSite):

Fig. 4–2: Configure parameters

4.1.1 SQL Server Configuration

The following parameters should be configured for the SQL server:

SQL server parameters

Name Description

Server Name This is the name of the SQL server or the server instance to be used.

Example: MyComputer\officeservers


11

Name Description

User Name User name for logging onto the SQL server. Only used when Windows authentication is deactivated.

Password Password for logging onto the SQL server. Only used, when Windows authentication is deactivated.

Windows Authentication Activate for using the actual Windows authentication for logging onto the SQL server.

4.1.2 Inter Server Configuration

For Inter Server, the following parameters should be configured:

Inter Server parameters

Name Description

HRef Set the HTML-Hyperlink of Inter Server

Example: http://MyComputer:89

Database Database for the Inter Server.

Example: InterServer

Fig. 4–3: Inter Server configuration

4.1.3 LogService Configuration

These are the parameters that should be set for the LogService:

Name Description

Database Database used for the LogService. Not used if the event log is used for logging.

Computer Computer on which the LogService will be running

Event log The event log will be used for logging.


12

Fig. 4–4: LogService configuration

4.1.4 Installed Programs

The following shortcuts are now found under Start > All Programs > SAPERION:

Program Component is installed... Description

Client Setup ...in every case. Selects the URL of the Configuration ser-

ver and the host name for Inter Server. The

URL for the Configuration server is http:/

/<servername>:<Port>/configserve.asmx. The

connection to ConfigServer and Inter Server can

be tested here.

Inter Server (Website) ...with Inter Server Opens the Inter Server web site.

ConfigServer (Website) ...with Configuration Server Opens the ConfigurationServer web site.

Install Application on ConfigServer ...with Configuration Server Installs and updates applications with this pro-

gram .

Inter Server Solution - SharePoint ...with SharePoint extensions Installs or removes SharePoint Solution for

2007 or 2010.

4.1.5 Folder Structure

The following folders are created in the <Program files>/SAPERION directory:

Name Description

Active Migration Manager Server Active Migration Manager

Inter Server Gather Files for the SharePoint Search

Inter Server Inter Server

4.2 Configuration

13

Name Description

Inter Server Web Inter Server website

ConfigServer Configuration Server data

ConfigServerClient Configuration Server utilities

ConfigServerWeb Configuration Server website

LogService LogService for database logging

MOSS2007Solution Installation programs for SharePoint 2007 archiving solution

Following folders are created under "%ALLUSERSPROFILE%\SAPERION":

Name Description

Inter Server Inter Server parts and configuration files

ConfigServer Configuration server data, including configuration of all services

JobService Active Migration Manager parts and workflow definitions

LogService LogService parts

4.1.6 System Services

To configure the system services:

1. From the Start menu select Administrative tools > Services

2. Set the "Login" to the service user you want to use, and then set the "Start type" to

"Automatic".

3. Start the service.

If the service does not start, check the event log for errors. For AMM and Inter Server, you can also start

console applications named AMMConsole or ARMConsole from the corresponding folder in “Program

Files”.

To get detailed information, check the log and debug log flags in the general configuration of the

application.

4.2 Configuration

Once you have completed the initial configuration of the Inter Server, you can use the various tabs in

the ConfigurationServer to configure more settings:


14

Fig. 4–5: Configuration server start page

+ Applications

You will find all installed programs under Applications. By selecting an application, you will be

taken to the application configuration. The configuration depends on the application selected. The

standard configuration is used for every computer without a specialized configuration.

To create a specialized configuration, make a copy of the standard configuration and change the

parameters for your computer.

+ Registered Applications

Under Registered Applications, you will find applications which had connection to the Configuration

server. If the application is a Windows service you will be able to start or stop the service.

The first start of the applications must be executed using the administration services. Set the

Startup-Mode to automatic, and set the identities to the service users you want to use.

Fig. 4–6: Configure registered applications

+ Event Log

If you have chosen the LogService, you will find event messages from all applications in the Event

Log. (Otherwise the information is found in the system event log.) You can filter the messages using

different parameters. Delete messages by using "Edit" > "Delete".

4.2 Configuration

15

Fig. 4–7: Configure event log

+ Compliance Log

In the Compliance Log, you will find messages relevant to compliance from all repositories. You

can filter the messages using different parameters. Which actions have to be logged for document

access are defined in the repository settings.

+ Workflow Monitor

The Workflow Monitor gives you an overview of the workflows controlled by the Active Migration

Manager.

4.2.1 Configuration Server Settings

All Inter Server settings can be configured using the Configuration server. Addins, Pipelines and the

System Repository are predefined. (You normally don’t need to change Addins and Pipelines.) If you are

planning to include Addins from third party vendors, ask the vendor for all necessary settings.

i The Inter Server must be restarted after every change to the settings.

1. Click "SAPERION Inter Server" on the Configuration Server start page.


16

Fig. 4–8: General Settings

2. The following settings can be changed:

+ HRef

Set the HTML-Hyperlink of the Inter Server to be used for references to documents.

Example: http://armserver:89

+ SQL connection string

SQL-connection string of SQL-Server.

Example: Server=sql\dbinstance; database=db1; Persist Security=False; Integrated

Security=SSPI;

+ System files

Select path of system files. If the field is left empty, the default path on installation

drive is created. (e.g.: C:\InterServer\_System)

Example: D:\SystemFiles

+ Temporary files

Select the path used for temporary files. If the field is left empty, the default path on the

installation drive is created. (e.g.: C:\InterServer\Temp) NOTE: No other programs

should use this path – Inter Server will clear this folder in regular intervals. (See

Appendix C for Cluster / NLB hints.)

Example: D:\TempFiles

+ Log Debug

Log all debug messages. For testing only.

Send all debug messages to the debugger. For testing only.

3. The following settings can be changed in the "Security" area:

+ Group for WebDAV access

When defined, only members of this group can access Inter Server via web folder.

Example: ARMuser

+ Group for HTML access

4.2 Configuration

17

Enter name of group that can access Inter Server via the HTML UI. NOTE: Requests

on single documents (GET) will never be rejected.

Example: ARMadmins

+ Local access only

Enable this switch if you only want to access the site from a local machine.

4. Following are the SharePoint settings that can be configured:

+ Content Disposition inline

Decide whether the content should be transferred in-line, or as an attachment

+ Content Disposition Extension

List the file extensions for in-line content disposition, separated by a semi-colon (;).

Example: .pdf;.jpg;.gif;.png

+ Search HREF for SharePoint

Define the HREF used for search results. If the field is left empty, a direct Inter Server

URL to the document will be used. If this field is changed, a full crawl of the content

is necessary to reflect the changes.

http://server/_layouts/ARMSearch.aspx?id={Path}

http://server/_layouts/

ARMSearch.aspx?id={Path}&host={Host}

http://server/_layouts/

ARMSearch.aspx?id={PathHex}&host={HostHex}

5. Also enter the settings for the Fulltext Cache:

+ Enable fulltext cache

Check to activate fulltext cache. You also have to activate the fulltext cache of the

repositories. All fulltext information will be stored in a database. NOTE that filenames

(including the path) may not exceed 450 characters.

+ Delete old entries access

Enter the retention period for fulltext entries in days. If no entries should be deleted,

enter 0.

+ Timeout in seconds

4.2.2 Pipelines Configuration

Every command sent to the Inter Server needs a pipeline for processing the request. All Addins connected

to the pipeline will be called serially. For example, the Addin ‚StdFilter’ will be executed as part of the


18

‚Put’-Pipeline. This Addin determines the extended properties of a given document using the Microsoft

IFilter and enters the properties for the document.

4.2.3 Addins Configuration

Addins are application parts implemented in DLLs. When creating a new Addin, the name of the DLL

must be defined. If the Addin needs additional parameters, you will be asked to input them.

4.2.4 Repository Configuration

Repositories are used to store documents. Different parameters must be given per repository. For a

description of repository-specific parameters, please read the appended descriptions.

i The system repository is the default repository. This repository cannot be used as a user data store.

The customizing of a repository is done by setting parameters and flags which influence the handling

inside the repositories. Most flags are common to all repositories and are shown in the system repository.

For detailed information on a specific repository, please read its supplement.

You must add a repository for your data before you start the Inter Server:

1. Click "Configuration Server" to open the configuration dialog in a browser window.

2. Click "Applications" in the menu bar.

3. Click "Edit" and then "Create new settings" in the drop-down menu.

Fig. 4–9: Create new settings

4. Select "Repositories" for the module, and "SAPERION-Repository (WebService)" for the

template.

4.2 Configuration

19

Fig. 4–10: Select

Click [OK] to close the window.

5. You are now on the configuration page of the SAPERION repository.

Fig. 4–11: Repository settings

Here you can configure the following settings:

+ System Repository Parameter

For a file-based repository, the path to the root, handling of properties and extended

features can all be specified.

+ Access Control

In general, you define whether a repository is active, read-only handling of security

(ACL), and whether files or folders can be deleted.


20

+ Compliance Logging

You can enable logging of a repository for auditing. If enabled, additional logging of

read or lock operations can be specified.

+ Index and Fulltext Options

For the support of search technology, there are some points to mention concerning

the protocol handler, fulltext handling from stubs and the Inter Server fulltext cache:

1. For the protocol handler, you can disable the repository, define logging

and define that metadata but no content should be crawled.

2. For stubs, you can disable the crawling of content.

3. You can include or exclude the repository from the Inter Server fulltext

cache (also has to be enabled in the general configuration, if used).

+ SharePoint Settings

For SharePoint integration, you define whether the repository can be used for

SharePoint archiving. You can either generally disable archiving from SharePoint, or

define a client (the definition of a client in SharePoint is part of the web site collection

properties; see the SharePoint documentation for details) and overwrite the HREF

which will be generated for the Search.

4.2.5 LogService

Logging information can be sent to the event log or to a database. If you use a database for logging, the

log service has to be started once in your environment.

Fig. 4–12: Start the LogService

The following settings can be configured using the Configuration server:

Name Description

Computer Name of the computer executing the LogService. NOTE: This entry is important! All applicati-

ons (using the LogService) will send their messages to this computer. If you want to transfer the

LogService to another computer be sure to stop all applications to avoid losing messages.

SQL-connection string Define the SQL-connection string here. The LogService will automatically create the needed ta-

bles.

5.1 Test the Server Functionality

21

Name Description

Eventlog Use the system event log for logging. If selected entries for Computer and SQL are not used.

5 Testing the Installation

5.1 Test the Server Functionality

To test the functionality of the server once the repositories have been configured, go to Start > Programs

> SAPERION > Client-Setup, and click [Test]. You should get a message that the test was successful.

Fig. 5–1: Test server functionality

5.2 Test the Repository Configuration

Next, check that the repositories have been configured correctly. Use the Inter Server Web View to do this:

1. Go to Start > Programs > SAPERION > SAPERION Inter Server (WebSite). Your repository

name should be listed.

Fig. 5–2: Repository name

2. Double-click the repository to open it. The archive folder(s) with the correct year(s) should

be listed.

5 Testing the Installation

22

Fig. 5–3: Repository folder year

3. Double-click the year folder to open it. Archive folders with the correct month and date

should be listed.

Fig. 5–4: Repository folder month and date

4. Double-click a folder to open it. You should see archive folders listed by HexUID inside.

Fig. 5–5: Repository folder hexUID

5. Finally, click one of the HexUID folders and check that the expected document is archived

inside.

Fig. 5–6: Repository file

When you have successfully tested your configuration, you can continue with the installation of Inter

Server Gather and Inter Server Solution.


23

i For more information about the Inter Server web interface, see Chapter 8, "Inter Server (Web

View)".

6 Installation of SAPERION Inter Server Gather

1. Click "SAPERION Inter Server Gather."

A warning appears. Click [Run]. The setup dialog ("Gather Installation") opens. Click

[Next].


3. Choose the installation folder. The default path given is

C:\Program Files\Saperion Inter Server\ARMGather

Fig. 6–1: Gather destination folder

You can change this path by clicking the [Change] button. Click [Next].


6 Installation of SAPERION Inter Server Gather

24

Fig. 6–2: Install Gather


Fig. 6–3: Finish Gather install


25

7 Installation of SAPERION Inter Server Solution -

MOSS 2007

1. Click the "SAPERION Inter Server Extension Solution" entry.

A warning appears. Click [Run]. The setup dialog for the Inter Server Solution installer

opens. Click [Next].

Fig. 7–1: Install Inter Server Solution


3. Choose the type of installation you would like, by clicking the corresponding button (the

different types of installations are described above).

4. Choose the installation folder. The default path given is

C:\Program Files\Saperion Inter Server\MOSS2010Solution

7 Installation of SAPERION Inter Server Solution - MOSS 2007

26

Fig. 7–2: Solution destination folder

You can change this path by clicking the [Change] button. Click [Next].


Fig. 7–3: Install Solution


27


Fig. 7–4: Finish Solution install

8 Starting Inter Server

The SAPERION Inter Server is installed as a Windows service. The service is started using the service

manager.

Fig. 8–1: Start Inter Server

For troubleshooting and debugging purposes, the installation folder contains the program

ARMConsole.exe. This program starts Inter Server as a console application. All messages including

debug output will be sent to the screen.

i If the service is running, you have to stop it before using the console.

9 License

28

9 License

If you are installing Inter Server for the first time, you have a full 30 days demo version. Once this period

expires, the program cannot be started again.

9.1 License Request

To request a license, use the license request button in the lower part of the Inter Server configuration.

By clicking the button, a license request can either be sent by email or downloaded.

9.2 License Installation

Once you have received the license, activate it as follows:

1. Select the "Upload license file" function from the Application / Configuration server page

for the repositories. This function is available through “Edit” in the Licenses region.

2. Enter the name of the license file or use the [Browse] button to select it.

Fig. 9–1: License activation

3. After successful installation, you should see a new line describing your installed licenses.

10 Inter Server (Web View)

Using the web interface, you can navigate the repositories as you do in a file system. Using the context

menu, you have access to the properties of the document, and you can view or define access rights.

10.1 Retention Period

29

i Access rights on folders are inherited. Depending on the repository, the storage of properties

and access rights differs. You can find detailed information in the Configuration Server Settings

section of this document.

If the repository supports retention periods, you can define these using the property menu.

A web folder view is supported. Inter Server supports the WebDAV-Protocol, so documents can be locked

during changes.

10.1 Retention Period

If the repository supports retention, you can also see the expiration date of the document, define the

retention or set the document on hold.

10.2 Security Settings

You can access the security settings using the "folder" or "file" context menu. If you have the necessary

rights, you can also change the security.

11 Appendix A. Installation Alternative

If you don't have SAPERION Inter Server, you can still access your SAPERION documents from

SharePoint, by configuring web part integration in SharePoint. (See the Microsoft SharePoint

documentation to learn more.) Then just link the URL of your SAPERION Web Client to the SharePoint

site, and the Web Client can be opened from within SharePoint.

12 Appendix B. SQL-connection strings

During configuration, the input of SQL-connection strings is often requested. Detailed information can

be found on:

http://msdn2.microsoft.com/en-en/system.data.sqlclient.sqlconnection.connectionstring.aspx .

13 Appendix C. Registry Entries

All registry keys are located relative to the key

HKEY_LOCAL_MACHINE\SOFTWARE\tecmasters\Active Repository Manager\1.0 .

All values are string values.

13 Appendix C. Registry Entries

30

13.1 General Settings

General Settings

Entry Description

defHost Default for Inter Server Host; is used when client does not present one.

defPort Port, default is 8086

defChannel Can have the values: http, ipc, tcp. Defines the channel type of connection. Default is tcp. NOTE: use tcp in

every case.

defConfigFile Configuration file used for remote configuration. NOTE: (absolute) path to file must be given completely,

and all user need read access to this file.

13.2 Mapping of Host Names

If you want to redirect a host to other hosts, you have to use the key mapped. Add an entry for every host

you want to redirect with an entry for the old and new host as value.

Example:

HKEY_LOCAL_MACHINE\SOFTWARE\tecmasters\Active Repository Manager\1.0\mapped\Host1 =

Host2

13.3 Extended settings of TCP Connections

Add a key named tcp (HKEY_LOCAL_MACHINE\SOFTWARE\tecmasters\Active Repository

Manager\1.0\tcp) and add entries as needed.

Entry Description

Name String defining the name of the channel. Default: ARMClientChannel.

machineName String defining the computer name used for the channel. In general you should use the DNS

name (Domain Name System) of the computers. If the IP address changes often for a network

card (Network Interface Card, NIC), e.g. q wireless connection, set the machineName for remo-

ting, so that the name can be resolved via DNS. If resolving a name is very slow, or you have to

use a special connection (VPN, virtual connection) use the IP instead of a name. Default: Not

set

priority Defines the priority to select this channel. The value is of type integer. Default: 1. A higher num-

ber mean higher priority. Negative values are allowed.

secure Boolean defines whether the channel is secure. Default: true Allowed values: true (1), false (0)

protectionLevel If "secure" is set, the default is EncryptAndSign. To change the ProtectionLevel on any other le-

vel than "None", the property "secure" must be true. NOTE that "None" is the only setting that

is compatible with Windows 95, Windows 98 or Windows Me. Default: EncryptAndSign. Allowed

values: EncryptAndSign, None, Sign

retryCount An integer setting the retry count. Default: 1.

13.3 Extended settings of TCP Connections

31

Entry Description

socketCacheTimeout An integer defining the time an unused socket is remaining in cache before removed. Default: 5

seconds.

timeout An integer defining the maximum wait time (in milliseconds) on a request before a timeout oc-

curs. The values 0 or -1 are defining an infinite period. Default: Infinite.

servicePrincipalName A string defining the servicePrincipalName for a Kerberos authentication. Default: null.

tokenImpersonationLevel A value of Type TokenImpersonationLevel. This property defines the authentication of the client

at the server. Default: Impersonation. Allowed values: Anonymous, Delegation, Identification,

Impersonation, None

domain A string defining the domain name to be used for authentication of the server channel. Will be

used together with username and password.

username A string defining the username to be used for authentication of the server channel. Will be used

together with domain name and password.

password A string defining the password name to be used for authentication of the server channel. Will be

used together with username and domain name.

14 Appendix D. Hints for clustered / load-balanced

installations

You will need licenses for every node of the system. For temporary files, the location must be a shared

folder is accessible by all nodes.

The Inter Server services need full access to this folder. These settings are configured in the Inter Server

general configuration settings.

15 Appendix E. Used Ports

The secure connection from any Inter Server Client to the Server uses port 8086. See Appendix B:

Registry-Entries for details.

The configuration service uses web services on port 1222. If a different port is desired, change it in IIS

and Client Setup.

The HTTP interface used with the Inter Server web site and direct Gets uses port 89. To avoid direct

access of port 89 in search, configure HREF for search using ARMSearch.aspx. See “Table 11 SharePoint

settings” for details.