Domain configuration file is usually named DOMAIN.xml (where DOMAIN is domain name) and is stored in configs directory. File can override almost all configurations specified in Tahiti.xml. Minimal domain configuration have to contain:

Each domain have separate working directory, local document database. All these items are stored in a directory call local domain repository. Domain configuration can be also stored directly in this directory and file have to be called domain.xml.

Example of domain configuration:

<?xml version="1.0"?>
<Config>
 <Item name="Connection.Domain" 
       value="lc.ucto.lightcomp.cz"/>
 <Item name="Connection.Name" 
       value="LightComp.Ucto"/>
 <Item name="Connection.Options" 
       value="...."/>
 <Item name="Connection.RequestConfig.DocumentTypes" 
       value="cmserver2.xml"/>
</Config>

If any of these two options is not defined configuration is invalid and cannot be used. List of valid configurations is displayed in the login dialog at Tahiti start-up.

Repository is created inside the user profile. It is possible to override this location in option Tahiti.Repository.Path. There are only few reasons for changing this location and we do not recommend to change it. Default location allow to use Roaming Profiles in Windows.

Domain configuration can be stored inside repository (not part of the configs directory) and all other configuration files can be downloaded from the server. This approach is suitable for the situation when there is one Tahiti distribution common for several domains. Domain configuration is stored at the file called domain.xml. It is possible to use utility called configDownload to download this configuration from the web server and store it at the right place.

There is special configuration option called Connection.RequestConfig.TahitiPacked. This is name of server side file with packed configuration. If this option is not empty configuration will be downloaded during logon. Tahiti is using MD5 sum to check if there is new configuration available.

Profiles are fundamental part of Tahiti and allow to customize look&feel to the specific needs, e.g. document viewing, scanning. There are several predefined profiles and administrator can change these or create new profiles. Default profiles are located in the directory bin/TahitiProfiles. Main file is profiles.xml and contains description of defined profiles. All profiles can be also redefined in domain specific settings.

<?xml version="1.0"?>
<TahitiProfiles>
 <Profile id="tahitiDefault"
    contentUrl="chrome://tahiti/content/intro.xul"
    saveChanges="0">
  <Name>Introduction</Name>
  <Name xml:lang="cs">Uvítání</Name>    
  <Name xml:lang="en">Introduction</Name>    
  <Description>This profile is used ....</Description>
  <Description xml:lang="cs">Profil použitý při ...</Description>  
 </Profile>
 <Profile id="tahitiDocViewer">
  <Name>Documents</Name>
  <Name xml:lang="cs">Dokumenty</Name>    
  <Name xml:lang="en">Documents</Name>    
  <Description>Recommended profile for ....</Description>
  <Description xml:lang="cs">Zobrazení ....</Description>    
 </Profile>
</TahitiProfiles>

It is possible to log several application activities. It can be used for diagnostic and debugging purposes. It is recommend to switch off logging in production environment.

Logging level should in interval <0; 4>. 4 is the highest logging level. Logging can be only set in the main Tahiti.xml.

Tahiti consist from several components. Each component have own configuration options and can be switched on/off. There are internal components (shared components) which are integral part of the application (through some of them can be switched on/off) and also there are domain components. Domain components can be used as plug-ins to extend Tahiti.

Not all work-places need all components and they does not have to be initialized. Switching-off can speed-up application start-up and use less system resources.

Tahiti can be extended with other components. There is configuration option called Components.XPCOM.Load. It is expected to receive comma separated list of components to be loaded. Components are physically stored inside directory Components. This option contains only domain components and cannot contain any shared components.

<Item name="Components.XPCOM.Load"
      value="@lightcomp.com/tahiti/sapgui.com;1">
</Item>

This chapter discuss communication between Tahiti (Document Manager) and other systems like document management system or information system. This chapter does not cover communication realized with other components and systems like DAMIS, Web, etc. These systems are described in separate chapters.

Tahiti allow communication primary with one document management system. It is called as Primary Connection. This connection should provide available document types, configuration. There is also possibility to communicate with more servers or use different communication protocol. Default and also the most powerful protocol is called DEP2. Protocol specification is available at the LightComp development web site. Each communication channel is configured by two items: used module name, configuration string.

PrintServer connection can be used for sending documents to the specialized printing service. This logic should be preferably realized on the server side but if it is necessary it can be done on the client side.

It is possible to write custom communication modules and customize Tahiti usage. Communication is configured with configuration string.

user=%TAHITI_DOMAIN%:%TAHITI_USER%; 
  password=%TAHITI_PASSWORD%; 
  server=sds.lightcomp.cz;
  port=7780; pingInterval=10;

Configuration string consist from pairs (name=value) separated by semicolon. Configuration is specific for each module.

user=%TAHITI_USER%;password=%TAHITI_PASSWORD%;
  server=192.168.0.1;port=7780;
  logLevel=4;logTarget=window  

user=%TAHITI_USER%;password=%TAHITI_PASSWORD%;
  server=192.168.0.1;port=7780;
  logLevel=4;
  cache1=%CSIDL_LOCAL_APPDATA%\LightComp\Tahiti\5.0\%TAHITI_DOMAIN%

Tahiti have system of internal variables. It is possible to use such variables in several configuration strings. Table contains some broadly available variables. Other variables are valid only in special cases.

Document processing in Tahiti is based on the MIME types. They are used for decision how to view and edit page. It is also possible in some cases find out corresponding MIME type from extension. Configuration files are used to set mapping between extension, MIME type and eventually to configure external application which is able to open it.

MIME type configuration is read in 3 stages:

The best approach is to view and edit file inside Tahiti. It allows to have control over user actions and also to know which application is used and how. If file format is not supported for direct opening it is stored in temporary directory and opened with default system application associated this file type.

<?xml version="1.0"?>
<MimeTypeDatabase>
 <MimeType type="application/msword" extension=".doc"/>
 <MimeType type="text/plain" extension=".txt" attr="2">
   %SystemRoot%\system32\NOTEPAD.EXE %1
 </MimeType>
</MimeTypeDatabase>
 

Help files can be defined as part of configuration process. Help can consist from files distributed together with application as well as links and URLs. Content of menu Help is defined in the Tahiti.xml. There can be up to five user defined items.

Each item have to have name and associated command. Configuration values: Help.User.X.Name - name, Help.User.X.Command - command to be executed. X is number in the interval <1, 5>.

 <Item name="Help.User.1.Name" type="string" default="&amp;Usage">
  <Description value=""/>
 </Item>
 <Item name="Help.User.1.Command" type="string" 
    default="%TAHITI_BIN_PATH%\help\index.html">
  <Description value=""/>
 </Item>