Install the Meridian API Service

Complete the following tasks prior to installation:

1. For Meridian Enterprise versions prior to 2019 R1, download the Meridian API Service installation package from the Accruent Customer Portal.

2. Uninstall any previous version of the API service.

3. Verify that the following are installed on the Meridian Enterprise server:

   • These components can be installed in advance:

     • Microsoft .NET Framework 4.6.1

     • Microsoft Internet Information Services

     • BC Enterprise website component

   • For use with HTTPS, the SSL certificate should be issued to the domain where the Meridian API is installed. Use a validated SSL certificate signed by a certificate authority (CA).

   • The Meridian Enterprise vault registered in the Meridian Enterprise Server configuration as described in Register a Meridian Enterprise vault.

   • A Meridian Explorer repository created in the Meridian Enterprise Server configuration as described in Create a Meridian Explorer repository.

   • A Meridian Explorer view configured for use by Meridian Mobile as described in Create and edit repository views. The following options must be enabled:

     • Accessible by the Meridian Explorer app for mobile devices option as described in Create and edit repository views.

     • Enable relational searches option as described in Configure miscellaneous search options.

     • For document and tag views, full-text search must configured as described in Configure miscellaneous search options.

   • A Meridian Explorer repository synchronization job configured and running without errors as described in Create a publishing job.

• The service will be installed under the Default Web Site in a virtual folder M360.Meridian\api as an application with the name of the current version being installed (for example, v2, v3, and so on). The files will be installed at C:\Inetpub\wwwroot\M360.Meridian by default.

• Only the default API path of https://<ServerName>/m360.meridian/<api_version>/ is supported.

• Users of Meridian Mobile must enter their user name as either:

  • <UserName> (local computer account)

  • <DomainName>\<UserName> (Active Directory account)

  UPN format (<UserName>@<DomainName>, for example) is not supported.

  They must enter the server name as either:

  • <ServerName>

  • <ServerName>.<DomainName>

• Service logs for troubleshooting are located in the folder C:\Inetpub\wwwroot\M360.Meridian\api\<api_version>\Logs by default.

• Meridian Mobile requires Meridian Explorer Standard or Meridian Explorer Plus licenses be registered on the Meridian Enterprise License Server.

• To allow access by Meridian Mobile users outside your organization's firewall, implement one of the following solutions:

  • Install the Meridian API Service on a web server running IIS in your DMZ. The web server will communicate via DCOM with the Meridian application server inside the firewall.

  • Configure a VPN on the mobile devices to provide a secure connection through the firewall to the Meridian API Service installed on an internal web server running IIS.

1. On the Meridian EDM server, start M360MeridianApiServiceSetup.msi.

   The setup wizard welcome page appears.

2. Click Next.

   The IIS Application Pool page appears.

3. Click options or type values using the descriptions in the following table.

4. Click Next.

   A progress page appears while the service is installed. When the installation is complete, the final page appears.

5. Click Finish.

   The setup wizard closes.

To install the Meridian API Service unattended:

• Run the following command line with the correct values for your environment:

  msiexec /passive /i "M360MeridianApiServiceSetup.msi"
      APPPOOL_IDENTITY_NAME="<AccountName>"
      APPPOOL_IDENTITY_DOMAIN="<DomainName>"
      APPPOOL_IDENTITY_PWD="<Password>"
      INSTALLLOCATION="<Path>"

Open the following URL in a browser:

https://<ServerName>/m360.meridian/api/<api_version>/checks/health

If the service is installed and working correctly, the service will return status: “Healthy”

The following table lists the available settings that can be configured by editing the application's web.config file.