Each of the Insight Components (server and client) use configuration files which enable them to run properly. Below is a list of Insight configuration files and configuration options:

Collection Manager and Personal Insight Manager

The Collection Manager is controlled by InsightServer.dat, which is used to set up database connections and manage the server. diacriticmappings.dat is used in indexing and to help with handling special characters.
Configuration files for the Collection Manager and Personal Insight Manager can be found inside the "Collection Manager" or "Personal Insight" directory inside the installation directory.

Task	InsightServer.dat	DiacriticMappings.dat
Changing the server's database connection - username & password database name hostname of the database server database port	X
Changing database SQL properties - escape characters & other information	X
Changing the debug mode	X
Changing the database debug mode	X
Changing the Collection Manager's port	X
Changing where server-managed files are created: Presentation files Group files Annotations	X
Changing the server timeouts	X
Changing logging settings	X
Specifying a media information table to store technical metadata	X
Private keys & connection information between the Media Manager and Collection Manager	X
Configuring alternate values for accented text (characters with diacritics) to enable better searching		X
Configuring Service Wrapper properties	X
Default Base URL for Themes	X
Default Base Path for Themes (filesystem)	X
Default BrowserInsight RemoteLaunch Base URL	X
Default Java Client RemoteLaunch Base URL	X
License Folder Location (pre-5.1)	X

User Manager

The User Manager is controlled by InsightUserServer.dat, which is used to set up database connections and manage the server.
Configuration files for the User Manager can be found inside the "User Manager" directory inside the installation directory.

Task	InsightUserServer.dat
Changing the server's database connection - username password database name hostname of the database server database port	X
Changing database SQL properties - escape characters - etc.	X
Changing the debug mode	X
Changing the database debug mode
Changing the Collection Manager's port	X
Changing Cross-Collection searching defaults (bg. Color / image)	X
Changing the server timeouts	X
Changing logging settings	X
Configuring Kerberos / LDAP authentication methods	X
Configuring Service Wrapper properties	X
License Folder Location (pre-5.1)	X

Media Manager

The Media Manager provides access to all images and media in Insight and runs as a servlet within Tomcat. The main configuration file for the Media Manager is the MediaManager.dat, located in the "media_manager" directory of the installation directory. A few other configuration settings (including the location of the mediamanager.dat are also specified in the server.xml.additions.txt and the web.xml).

Task	MediaManager.dat	Server.xml additions	Web.xml
Where the servlet is located and servlet startup / reload properties		X	X
Servlet name and URL		X	X
Where the mediaManager.dat file is located	X
Where media is stored	X
The max resolution managed by the Media Manager	X
Debug level	X
Where the SID Server is	X
Private keys & connection information between the Media Manager and Collection Manager	X
Logging information	X
Ticketing properties for the Media Manager	X
License Folder Location (pre-5.1)	X

BrowserInsight

BROWSER INSIGHT IS NO LONGER SUPPORTED BEYOND 6.2

BrowserInsight is the server component that manages access for the browser components and runs as a servlet within Tomcat. The main configuration file for BrowserInsight is BrowserInsight.conf, located in the "browserInsight" directory of the installation directory. A few other configuration settings (including the location of the BrowserInsight.conf are also specified in the server.xml.additions.txt and the web.xml).

Task	BrowserInsight.conf	Server.xml additions	Web.xml
Where the servlet is located and servlet startup / reload properties		X	X
Servlet name and URL		X	X
Where the BrowserInsight.conf file is located	X
User Manager address	X
Default username and password	X
Debug level	X
Access logging settings	X
Private keys & connection information between the Media Manager and Collection Manager	X
SSL settings	X
Collection database configuration settings (per collection available in the browser)	X
Max Values available in a speed search	X
License Folder Location (pre-5.1)	X

XML Gateway

The XML Gateway is a middleware component that provides access to Insight's content to XML-aware applications and runs as a servlet within Tomcat. The main configuration file for the XML Gateway is web.xml, located in the xmlgateway/servlet/WEB-INF/ directory of the installation directory. The XML Gateway is also controlled by the server.xml.additions.txt.
Table 21: XML Gateway Configuration Files

Task	Server.xml additions	Web.xml
Where the servlet is located and servlet startup / reload properties	X	X
Servlet name and URL	X	X
Debug level		X
User Manager Address		X
Username and Password for User Manager		X
Unknown character replacement character		X
License Folder Location (pre 5.1)	X

Insight Client Applications

Please see Table 20: Consolidated Properties by Client Application on page .

Insight Administrator Tools

The Administrator Tools maintains a configuration file (insightadminstore.dat) which should not be edited by hand.

Introduction to the Insight Configuration Files