The Connector Framework

• Architecture
• Connector Content
• Connector Database
• Enabling the database
• Licensing
• Security

Overview

This section explains the design, purpose, and architecture of the Connector.

The architecture shows how the framework fits together and links M‑Files with SQL; the data model depicts the relationships between the tables; and the different components of the framework are outlined with their role and function.

The use of T‑SQL procedures and functions is introduced here. Their application is covered in subsequent sections.

Finally, we outline the use of CLR as a fundamental building block in the design.

Purpose and scope

The sole purpose of the Connector is to enhance the application of M-Files using Microsoft SQL Server. The licensing, use and support for M-Files and Microsoft SQL is assumed and separate from the Connector.

M-Files helps enterprises find, share, and secure documents and information. At the same time, the integration with and access to Microsoft SQL as the database, exposes the M-Files metadata for a range of different types of applications. The Connector:

• Enables reporting on any metadata with static or dynamic reports, with near real-time availability of data.

• Allows for extensive metadata re-alignment, cleansing, or manipulation.

• Enables building interfaces and integrations with bespoke applications or other third-party systems.

The use and configuration of M-Files and SQL Server is not included in this document. Refer to the respective product documentation for further details.