Setting Up Both Web Clients and M-Files Mobile

The steps given here tell you how to enable these clients and services:

  • M-Files Web
  • Microsoft Office for the web services for M-Files Web
  • Classic M-Files Web
  • M-Files REST API
  • M-Files Mobile

Make sure that these requirements are completed:

Important remarks:
  • If M-Files Web was previously set up on the server with the instructions in Setting Up the Backend for the New M-Files Web and Web-Based Add-Ins: We recommend that you remove the old configuration before you set up M-Files Web with the instructions given here.
  • If you get an error during the setup, exit the wizard, fix the issue in IIS Manager, and start the wizard again. The error can be, for example, that a newly created website cannot start because the port number is already in use.

Do these steps:

  1. Open M-Files Admin on the server.
    Important: If IIS and M-Files are on separate servers, see Using Proxy Setup with M-Files Web instead of the instructions given here.
  2. In the left-side tree view, select a server connection.
  3. Click Set Up Web and Mobile Use > Set up M-Files Web, classic M-Files Web (and REST) and M-Files Mobile > Next.
  4. Select one of these options:
    OptionResult and instructions
    Use an existing website

    Use an existing Internet Information Services site for M-Files Web.

    In the drop-down menu, select one of the available sites.

    Create a new website

    Create a new Internet Information Services website for M-Files Web.

    Enter the name and TCP port for the site. Make sure that the given port number is not already in use.

    Note: You can use this option only with a server operating system.
    Create a new virtual directory

    Add a new virtual directory to the selected Internet Information Services website and use the directory for M-Files Web.

    Select an available site and enter a name for the virtual directory.

    Note: You can use this option only with a server operating system.
  5. In Site Binding Address, enter a site binding that the M-Files application server can use to reach the IIS proxy server computer.

    It is not necessary to use HTTPS or the port 443. You can also use HTTP and any other port or binding available on the IIS server. For example, if the IIS proxy uses a self-signed certificate for the website binding, you must use HTTP because M-Files does not support self-signed certificates in this context.

    If you have many vaults or many DNS names for the IIS sites, we recommend that you use the IP address of the IIS server as the site binding address. It can be necessary to create an appropriate binding on the IIS site for this purpose. For example, the binding normally allows any incoming traffic for the IIS server IP.

    For a virtual directory, include also the directory name. Refer to the table and this article for examples and more information.

    Example Site binding address Port Directory name 80 - 8800 M-Files
  6. Optional: If IIS and the M-Files server are on separate servers, enable Use proxy server setup and enter the app server address to use a proxy environment.
    For instructions on how to set up the proxy server and the site binding address, see Using Proxy Setup with M-Files Web.
  7. Click Next.
  8. Optional: Enable Use M-Files Web as default web client on this server.

    Before you continue, read the information on the page carefully.

    If this setting is not enabled, the classic M-Files Web is used as the default client. This also lets you control the default web client vault-specifically. See Changing the default web client vault-specifically.

    If you use OAuth-based authentication in the vault, the default web client setting can have an effect on the endpoint settings of your configuration. For more information, refer to Setting Up OAuth 2.0 for the New M-Files Web and Web-Based Add-Ins.

  9. Click Save.
  10. Open the Document Vault Advanced Properties dialog and add the M-Files Web URL (or URLs) according to the IIS bindings.
  11. After 20 to 30 seconds, enter your website address in a browser and make sure that the client opens (or clients open) correctly.

The users can now open the web clients with the addresses given here.

M-Files Web set as the default client:

Client Address Example
M-Files Web <server address>
Classic M-Files Web <server address>/login.aspx
REST API endpoint <server address>/REST

The classic M-Files Web set as the default client:

Client Address Example
M-Files Web <server address>/vnext
Classic M-Files Web <server address>
REST API endpoint <server address>/REST