M-Files Installation¶
Release 4 introduced installing selected components into the M‑Files vault as part of the Connector. The Connector will not operate without these vault components. The Database File Connector (IML) application is optional and requires an IML license.
Components¶
Component |
Scope / Contents |
Purpose / Notes |
---|---|---|
Content package |
Objects: MFSQL Connector; Classes: MFSQL Configuration, User Messages; Properties: MFSQL Class Table, MFSQL Count, MFSQL File Unique Ref, MFSQL Message, MFSQL Process Batch, MFSQL User, MFSQL Configuration, SettingsDetail, SettingsName; Groups: ContextMenu, MFSQLConnector; User: MFSQLConnect; Views: User Message; Workflows: ContextMenuFlow, MFSQL Messages; Example action scripts. |
SQL user messages in M‑Files; ODBC connection settings; User feedback on objects; Database file imports; SQL procedure calls from M‑Files; Context menu security. |
MFSQL Connector vault application (VAF) |
Licensed vault application that coordinates operations between M‑Files and SQL. |
Enables interaction between M‑Files and SQL via Connector procedures. |
Context Menu UI extensibility application (UIX) |
Adds user actions in the M‑Files UI. |
Allows calling Connector procedures from M‑Files in multiple ways. |
Database File Connector (IML) |
IML connector for database files; license controlled. |
View and search database file BLOBs from M‑Files. |
Availability¶
Module |
Release |
---|---|
General |
4.1.5.41 |
Tip
The installer deploys all required components automatically. You can also install them manually by following the instructions in the installation section.
Warning
The Connector will not operate without the M‑Files vault components from Release 4.