Damaris LDS Functionality
1 – How Damaris LDS Works ?
Damaris LDS stores index information in database and electronic documents in Jukebox.
So, when you need to setup export tasks, you have to configure tools to access to these 2 resources.
To view or print a document Damaris LDS reads document’s storage information from database and reads data from Jukebox.
Several electronic document types exist:
Type Value
in database |
Type explanation |
0 | Spool without overlay |
1 | Spool with overlay |
2 | |
4 | TIFF file |
9 | Native file (PDF for example) |
For each type, Damaris LDS uses different method to construct the page.
1.1 – FDI Language
In Damaris LDS we developed a graphical language close to XML which permited to create vector overlays including fixed text, logo and some graphical objects like rectangle, line, etc.
FDI (Format de Documents Indépendants) is heavily used by Damaris customers.
Damaris RM also offers a new modern approach of the same language by providing an FDI Designer WysiWyg tool.
1.2 – Overlay Management
The idea here is to construct a page containing data and an overlay which facilitates readability.
Generally, a standard document like invoice or pay slip has the same shape for all documents, only data changes from one document to another.
In Damaris LDS we have several systems to manage graphic part of each document.
The following table sums up existing overlay management:
Overlay Management Mode | Explanation |
0: No Overlay | |
Image Overlay | A TIFF image is used as overlay. In this case image file is named DOCUM.SMP (Where DOCUM is the document type’s code). |
Vector fixed Overlay | An FDI file is used as overlay. The FDI file is also named DOCUM.SMP (Where DOCUM is the document type’s code). |
Vector overlay with positioned fields | An FDI file contains vector objects, fixed text and logo.
It also contains fields extraction from incoming text file which are positioned in the page. Designer can also choose text attributs like font, size, color, etc. |
Vector overlay with positioned fields and Index extraction | Same as previous mode, but in this case index extraction from text file is also described in FDI file. |
SMP and FDI files are stored in a directory.
Path to this directory is configured in LDSEngine.INI file:
[LDSENGINE]
Répertoire d’application=PATH_TO_OVERLAYS
Be aware that in some cases you may find overlay files named DOCUM.001 002 etc.
These files contain overlay data depending on LDSEngine’s configuration able to call the right overlay depending of data value present in text file.
2 – Export Tools
The principal module to export documents from Damaris LDS is Damaris Engine Control (DEC).
DEC is a module which executes tasks.
Each task is linked to a Plugin.
Here, we will use GetPage plugin.
3 – DEC environment for Documents Export
Here is a schematic view of different components:
As you see, you have to ensure that DEC is connected to databse by using ODBC DSN connector.
4 – Detailed information
4.1 – DEC Database tables
When installed, DEC creates several tables. Here are explanations about each one:
Table Name | Explanations |
D_JOBSPLGPARAM | This table contains global parameters used for all tasks
For export process (GatPage Plugin) you need one mandatory row to configure path to LDSEngine.ini. |
D_JOBSNAME | Lists all installed plugins |
D_JOBS | Each row is one task.
Contains information about each task. JOBSTATE column indicates job’s state. Here are values accepted in this column:
|
D_JOBSPARAM | Gives all specific information for a given task in D_JOBS.
In our case, D_JOBSPARAM will have all parameters for GetPage Plugin. |
D_LOG | Contains all log information after a task is executed. |
4.2 – LDSEngine.INI Content
This configuration file will provide the following information:
- Path to Jukebox
- Indicates where Damaris LDS or DEC GetPage will find archived documents
- Path to Overlays (FDI)
- Where to find SMP or FDI files
- Path to Temporary Directory
- Where Damaris LDS or DEC GetPage will store temporary files needed to construct final document
Please note that in old Damaris LDS installations you may find LDS32.INI instead of LDSENGINE.INI file.