Architecture

In order to expose the M-Files metadata, the Connector imports the data from M-Files using the LSConnect Wrapper assembly that wraps the interop.MFilesAPI and bi-drectionally update the SQL Server using a range of T-SQL procedures that interacts with the assembly.

The current release of the Connector include most of the M-Files metadata and object details of the target vault.

The Connectors always operate on a single designated vault in the M-Files Server. A separate Connector is required for every vault that requires interaction.

The Connector is installed on the SQL server in a separate database. This SQL server may be on the M-Files server or another server as long as the Connector server and M-Files server can be connected. A cloud vault will connect to SQL using a web service.

Note that the Connector does not require nor use the standard M-Files SQL vault database. The Connector operates a completely separate and independent SQL Database from the internal M-Files SQL Database.

Version 5

Up to version 5, MFSQL Connector does not require a connection from M-Files to SQL. This connection was optional in previous versions to allow for some operations to be initiated in M-Files. By enlarge the previous versions allowed a user to initiate most operations using SQL with a connection from SQL to M-Files.

Version 5 introduces a range of new user operations and automation that reduces the need for the user to use SQL to accomplish the task. These operations are actions in the vault administration module or the client (both desktop or web). These operations will require a connection from the vault to the SQL Server.