Technical Architecture for v5.0

Installing and Configuring DocuNECT v5.0


This information applies to v5.0 DocuNECT versions.

DocuNECT has the following main components:

1) DocuNECT Server. A server is a Windows service that has two primary functions. The first function is to execute the ContentConnectors which manage a number of different document related processes. Refer to the ContentConnector Library for more information. The second function of the service is to manage the file I/O from the storage locations. The service uses port 7001, which will need to be open on all DocuNECT stations. The station also includes the install for the DocuNECT Document Framework (.NET and Services) that manages provides all the document capture and management functionality.

2) DocuNECT Station. A station is an instance of the DocuNECT server registered within a DocuNECT database. One server can service multiple stations registered in different databases.

3) DocuNECT Lifecycle Server. This component contains the Document Lifecycle document processing functionality and also the Document Lifecycle Editor (The editor install was combined with the runtime in v4.2.1.1 onwards).

4) DocuNECT Database. The Microsoft SQL Server database stores all configuration and document information and also links to the documents while they are going through the Document Lifecycle process. The actual documents are stored on a designated DocuNECT storage location attached to a station.

5) DocuNECT Web. This is a .NET based Web application that works with Microsoft Internet Information Server (IIS) that is the primary interface to the documents and data.

6) DocuNECT Client Tools. The desktop capture tools communicate with the DocuNECT server environment via the DocuNECT Document Framework Services.

techarchitecture.jpg

An Overview of the DocuNECT Document Framework

The Document Framework sits at the heart of DocuNECT and provide programmatic access to all the different features of the document lifecycle, document management, workflow, retention, and administrative functions.

There are two versions of this framework, a version based on Microsoft's .NET Framework v4.0/v4.5 and one based on web services. The .NET version provides all functionality that is used by the DocuNECT Web application, both document and system administration functions. The web services framework focuses on the document related functions and is used by the client tools and dashboards.


An Overview of the Database Structure

DocuNECT is a database driven document management environment. All configurations are held within a Microsoft SQL Server database in both the express and full versions. In DocuNECT terms a database can be described as a distinct repository of information storing the following objects:

  • Stations - Run connectors that are configured in the database.
  • Security - User, groups and permissions.
  • Storage Locations - Different content storage locations.
  • Cabinets (formerly Index Configurations) - Document indexing configurations data.
  • Lifecycles - The lifecycle describes the stages the documents goes through during its life.
  • Business Data - Additional data tables can be created and accessed to manage business data to support the different processes being configured.
  • Document Data - Stores all data on the documents including a relative path link to the external storage location that houses the actual documents stored in native format. The data also includes the complete document's complete lifecycle including records retention and workflow.

One database can manage multiple document management scenarios. However, different DocuNECT databases can be used to manage documents from different companies. In a typical implementation there are usually two repositories, one for development and one for production.


Implementation Models

DocuNECT allows for the following implementation models:

  • Single-Server (Local Database). One implementation of the DocuNECT Server, DocuNECT Capture Lifecycle Server, database, and DocuNECT Web components residing on the same server.
  • Single-Server (Remote Database). One implementation of the DocuNECT Server, DocuNECT Capture Lifecycle Server, and DocuNECT Web components residing on the same serer with the database residing on a remote server.
  • Enterprise Multi-Server (Central Database). For an enterprise implementation the DocuNECT Server, DocuNECT Capture Lifecycle Server, database, and DocuNECT Web components can be installed on separate servers.

Scalability

Docent is highly scalable and can support the following configurations:
1) The DocuNECT Web client interfaces can be load balanced with different IIS instances to better manage the throughput of users requests and traffic.
2) Multiple stations and DocuNECT servers can be added to an environment to increase the processing of document/data transactions and lifecycle processes.
3) Stations can monitor themselves and can be dynamically moved to other station to better utilize resources.
2) The databases can be clustered using Microsoft SQL Server clustering.


Component Compatibility

The Component Compatibility page provides a complete lists of compatible software components and operating systems.


Hardware Specifications

The Hardware Specifications page provides typical hardware specifications to act as a guide for planning a new system implementation.