Table of Contents
Program is designed for Microsoft Windows 2000, XP, 2003, Vista, 2008 and later editions. Tahiti is fully 32-bit application. Program can be used together with terminal services on Windows 2000, 2003, 2008, Citrix – there are no explicit restrictions but some can exists which are given by these systems (e.g. color depth). Usage of scanners and digital cameras together with terminal servers is not recommended and can be problematic.
Hardware requirements depends on used operating system. It also depends on the way of Tahiti usage (workplace type), document types and their sizes. For scanning workplace's consult hardware requirements with scanner manual and also take a look in the chapter about scanning.
Table 2.1. Minimal configuration
Processor | Pentium II 400+ |
RAM | 256Mb, recommended 512Mb |
Graphical card | 1024x768x16bits |
Appropriate pointing device is essential. Program is design to run in dual head configuration (two monitors). It is usual to run application for access to the information system on one monitor and Tahiti on the second one. Application support such usage.
Tahiti can be resource consuming application. It depends on way of usage but it can be caused by:
parallel opening of higher number of pictures (photos)
work with embedded objects (OLE2)
scanning with some transformations, smart quality control, bar-code recognition etc.
Tahiti is graphical application and it is recommended to have enough system resources for efficient usage. It is also very important to train users for proper use of Tahiti. We know from our technical support what users are able to do. So please do not underestimate good training.
Tahiti is design to be run on Microsoft Windows 2000 and later. From version 5.x Windows 2000 are not fully supported and we recommend to use Windows XP or later. Tahiti is registered in the system as a COM Server and requires proper registration. Check installation section for more information about required libraries and their registration.
Tahiti is distributed in two forms:
MSI package (Microsoft Installer) - end user installation file
ZIP file - contain all Tahiti files and also SDK
You can create your own customized distribution/installation package - based on MSI or use othe installation program (InstallShield, InnoSetup). Such package have to comply with License Agreement.
Tahiti starting from the version 5.0.4 is distributed as MSI package. It is currently preffered way of distribution. One package can be used for end-user installation and also can be customized by administrator. Check chapter MSI Customization for more details about MSI customization.
ZIP file contains binary files, documentation, configuration files, examples, add-ons and also SDK (Software Development Kit). File can be used by developers (to use SDK) or by system integrators and administrators to create own custom install. Following table shows distribution layout.
Table 2.2. Distribution layout
| Path | Description |
|---|---|
| binary files, main application |
| Chrome files for Tahiti and Xulrunner |
| xpcom components |
| configuration directory |
| Xulrunner default configuration |
| Tahiti-Mozilla preferences |
| localization packages, cs - Czech, ru - Russian |
| log files are stored in this directory (if enabled) |
| scanner control dialog |
| example of configuration |
| Documentation (.chm, .pdf) |
| Administration guide |
| Programmers guide |
| Separators for scanning |
| examples of SAP integration |
| Tahiti extensions |
| Bar code recognition, need separate license |
| FastReport |
| Redistributation files (runtimes required by Tahiti) |
/sdk | Software Development Kit for Tahiti |
/sdk/addons | Addons for 3rd party applications (Lotus Notes) |
/sdk/bin | Binary files for SDK (tests, utilities) |
/sdk/samples | Examples of various types, scripts, etc. |
/sdk/samples/DataForms | Examples of data forms - used for data-mining |
/sdk/samples/forms | Examples of Tahiti simple forms |
/sdk/samples/packages | Examples of Tahiti Packages (.tpkg) |
/sdk/samples/sap | Examples of SAP integration objects |
/sdk/samples/vbscript | Examples of Visual Basic Scripts (.vbs) |
/sdk/xpidl | XPCOM interface definition files (.idl) |
/setup | Default setup script for InnoSetup |
| list of changes |
To prepare your own installation package you should consider
using of MSI based installer. You can use classical installation
products like InnoSetup. In such case it is up to you to prepare
distribution plan and distribution itself. However there are
pre-prepared setup configuration files. For larger organizations we
recommend to use Invoker for distribution and installation. Invoker is
separate application for automatic updates and installations.
You can skip this section if you are using MSI based installer.
Installation depends on way of usage and customization for given
workplace. In general you should install all files from the
bin directory and include also other files like
your own extensions and add-ons. Description of all files is in separate
paragraph. Default and recommended directory for installation is
Program Files\LightComp Tahiti 5\ . User
configuration should be done in domain
configuration files, these are installed in the
configs directory.
Some of the files have to be registered during installation.
Table 2.3. Files to be registered
| Name | Description |
|---|---|
/bin/BarcodeControl.dll | Component for barcode generation |
| Microsoft Excel integration |
/bin/IEHelper.dll | Internet Explorer integration |
| Microsoft Outlook integration |
| Definition of Tahiti COM interfaces |
| Component used for document processing and automation |
| Component for MSG conversion |
| Microsoft Word integration |
| Component for SAP integration |
| Main application (run Tahiti.exe /Register) |
Tahiti can be run from main directory clicking on the file Tahiti.exe or using COM interface (detail description is in the Programmers Guide). User have to select domain, offline or on-line mode. It is not possible to send or receive any data in offline mode. Tahiti is usually executed without any parameters.
Tahiti will alwasy run as 1 process for several domains.
Table 2.4. Tahiti parameters
| Parameter | Description |
|---|---|
| /d <domain> | Domain to be used. |
| /offline | Automatically run Tahiti in offline mode. |
| /password <password> | Password |
| /profile <name> | Use specified profile. This option can be used to force
Tahiti to use profile. 'name' is name of file profile as
defined in the profiles.xml . E.g.:
/profile tahitiDefault will read configuration
from file tahitiDefault.xml. Profile will be read only if
domain is specified. |
| /user <user-name> | User name |
During the installation process Tahiti have to be properly registered. All required .dll files have to be registered and also main binary. To do this step there is set of parameters. Do not use this parameters together with regular parameters.
Table 2.5. Tahiti parameters
| Parameter | Description |
|---|---|
| /Register | Register Tahiti.exe |
| /Unregister | Unregister Tahiti.exe |
| /Embedding | Run Tahiti in embedding mode (used for COM) |
| /Automation | Run Tahiti in automation mode (used for COM) |
Tahiti requires local document repository where are stored
documents, working files, user configurations. Repository is usually at
the Documents and Settings\USER\Application
Data\LightComp\Tahiti\5.0\. Some working files, cache etc are
stored in the location of non-roaming profile, typically at
Documents and Settings\USER\Local Settings\Application
Data\LightComp\Tahiti\5.0\. Default location can be override
in configuration, parameter Tahiti.Repository.Path.
Repository contains several files and directories. Files and directories bellow are part of the roaming profile. If user log on another computer within Domain (Active Directory) these files will be shared.
Table 2.6. Repository structure
| Name | Type | Purpose |
|---|---|---|
settings.xml | file | User settings |
| file | Domain specific configuration files, document types etc. |
| file | Actual toolar/user interface layout |
| file | active copy of file defining document types - older format |
| file | active copy of file defining document types - newer format |
| file | Configuration file for the domain. This is
optional file - domain configuration can be read from this
file or from file in the |
| file | active copy of file for displaying document hierarchy |
| directory | scanned batches |
| directory | history records |
| directory | tool-bar layouts |
| directory | thumbnails cache, part of the local (non migrating) profile |
Directory can contain other configuration files downloaded from
the server. These files have higher precedence then files in the
configs directory.
Repository contains several files and directories. Files and directories bellow are part of the roaming profile. If user log on another computer within Domain (Active Directory) these files will be shared.
Table 2.7. Repository structure
| Name | Type | Purpose |
|---|---|---|
camel-cert.db | file | Certificates used by mail component |
| directory | Working files (temporary). |
| directory | Mozilla security database (keys, certificates). |
| file | object database of local repository |
| directory | contain binary data for documents in local repository, part of the local (non migrating) profile |
| directory | contain data for Damis system (downloaded packages). |
Tahiti have direct support for several document and image types. These are opened inside Tahiti and can be viewed and edited. Document type is determined by MIME type provided for given file from information system or by operating system. File types which does not have direct support are opened in external application.
It is essential to establish rules which defines supported MIME types and application used for such files. Tahiti can be configured in several ways. There is brief overview of supported types.
Tahiti can view and annotate several image types. Usually TIFF files are used for storing scanned images and JPEG files for photos. TIFF often serve as a container for several other file formats like CCITT G3, G4, etc. Tahiti have extensive support for TIFF variants.
Table 2.8. Image view supported types
| Extension | MIME type | Description |
|---|---|---|
bmp | image/bmp | Windows or OS/2 Bitmap |
cut | image/freeimage-cut | Dr. Halo |
g3 | image/fax-g3, image/g3fax | Raw G3 fax |
gif | image/gif | GIF image |
ico | image/x-icon | Windows Icon |
iff,lbm | image/freeimage-iff | IFF Interleaved Bitmap |
jpg,jif,jpeg,jpe | image/jpeg | JPEG - JFIF Compliant |
jp2,jpc,j2k | image/jp2 | JPEG-2000 JP2 File Format and JPC Code Stream Syntax (ISO/IEC 15444-1) |
koa | image/freeimage-koala | C64 Koala Graphics |
mng | video/x-mng | Multiple Network Graphics |
pcd | image/x-photo-cd | Kodak PhotoCD |
pcx | image/x-pcx | Zsoft Paintbrush |
png | image/png | Portable Network Graphics |
pbm,pgm,ppm | image/freeimage-pnm | Portable Network Media |
psd | image/freeimage-psd | Adobe Photoshop |
ras | image/x-cmu-raster | Sun Raster Image |
tga,targa | image/freeimage-tga | Truevision Targa |
tif,tiff | image/tiff | Tagged Image File Format |
wap,wbmp,wbm | image/vnd.wap.wbmp | Wireless Bitmap |
xbm | image/x-xbitmap | X11 Bitmap Format |
xpm | image/xpm | X11 Pixmap Format |
Tahiti is OLE2 container. It means it is possible to work with Word, Excel and other documents inside Tahiti. There is special support for Microsoft Office documents. Lot of OLE2 servers have small differences in behavior and might need some integration work. Fully tested and recommended are Microsoft Office versions 2000, XP, 2003, 2007, 2010.
Text files are expected to be in local machine encoding. Information system should not use text files directly but preferable other file formats, like for example HTML for read-only documents.
Internet Explorer is one of embedded containers inside Tahiti. It allows to display HTML files but also PDF files and other read-only formats. Adobe Acrobat should be installed. It is possible to use other alternative applications which have plug-ins for Internet Explorer.
It is possible to display .TFR files (Tahiti Form). Tahiti has support for simple form processing. They can be used for data mining or other tasks where user input is required. There is special chapter about form processing and creation.
Files with extensions TPKG. Such files are packed files which contains transformation script, document/report template and instruction how to process. Such files are processed on the client side and can produced Word, Excel and other documents. Packages are often used for personalized letter and reports. There is special chapter on this topic.
Tahiti can be used to view and edit email's. It it possible to
integrate writing/reading email's with work-flow events. Email's can
be archived and identified same way as images and other documents.
Email support is described in separate chapter. Tahiti in general
handle mimetypes: message/rfc822,
application/msoutlook. New-ly created or
replied emails have mime-type
Tahiti.ComposeEmail.