Kofax DM API - Manual (Page 23)

T HE DM A RCHITECTURE 3
DM Functionality
The DM Server is a transaction server, similar to Microsoft SQL Server.
The DM Server manages database connections via a connection pool.
A client application connects to the DM Server via DCOM (Distributed
Component Object Model) interfaces that are typically free threaded.
The DM executable file (DOCSFusion.EXE) loads COM objects
configured in the registry. Once connected, users can connect to any
repositories to which they have access rights.
DM is stateless, so the client does not remain connected to the DM
Server. A client application submits a transaction using a document
security token (DST), and DM then determines the validity of the DST.
If the DST is valid, the DM Server processes the transaction and returns
the results to the client software. No state information is kept by the
DM Server about the client.
Note: DM enforces document security rights. Users cannot access objects (for
example, documents or folders) to which they do not have rights.
In DM, library maintenance tasks such as archiving and full-text
indexing occur in the background, and there is no native user interface
(UI). (To simplify these diagrams, DM Indexer Servers are not shown.)
Developers must create user interfaces to connect to the DM Server.