Meridian Application Server Requirements

Lesser specifications might be insufficient to configure HyperCache. For more information, see Hypercache.

• Dedicated server that is not used for anything other than Meridian and its database engine, SQL Server or Oracle.

  We recommend only the Enterprise hardware specifications when Oracle or SQL Server are used on the same computer or with multiple active vaults.

• One of the Windows Server operating systems (with latest Service Pack) listed in Operating Systems.

  The operating system should be installed with the roles and services described in Server Role Requirements.

• Microsoft .NET Framework 4.7.1 Full Profile (the Client Profile is insufficient)

• Any additional requirements for specific operating systems or Meridian releases that are documented in the 2024 Release Notes.

• If the vaults will not be hosted on the Meridian application server with the Hypertrieve database engine, a connection to one of the database management systems listed in Database Management Systems.

  • If any vaults will use a Meridian Enterprise MS SQL Server 5 (or later) database engine to connect to either a local or remote SQL Server instance, the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) must be installed on the Meridian server.

  • If any vaults will use the Meridian Enterprise Oracle 5 database engine (not Oracle 3) to connect to either a local or remote Oracle instance:

    • The 64-bit Oracle Data Access Components (ODAC) and Oracle Data Provider for .NET (ODP.NET) version 11.2 or higher must be installed on the Meridian server.

      For more information about database engine selection during vault creation, see Create a New Vault.

    • A default installation of Oracle is limited to 150 processes.

      If the database server has more than one CPU, that limit may be reached and cause vault errors, especially during large imports. We recommend that you configure Oracle to allow up to 500 processes.

• The vault audit trail feature of the Meridian FDA Module and the subscriptions feature of Meridian Enterprise require a connection to one of the database management systems listed in Database Management Systems.

• Microsoft Access installed in advance.

  Microsoft Access is the default storage for external lookup tables. We install SQLite as the default for storing local workspace data. Microsoft Access is not used for vault data and is not installed by the Meridian setup programs. You can use Enterprise Server or Microsoft Access for your user database.

  The lookup tables (but not the user account database or local workspace databases) can also be stored in a server edition of SQL Server. The supported versions of SQL Server are listed in Database Management Systems. Storage in a server edition has the following limitations:

  • Lookup table entries will not be included in the vault configuration export (.met) file. Therefore, they cannot be imported for use in another vault unless that vault is also connected to the same database server.

  • Lookup tables will not be included in the vault backup snapshots and must be backed up separately.

  • Retrieving lookup table entries and using them in custom property pages requires VBScript programming. The database connection strings will be encoded in the scripting, which may pose a security risk for your organization and will require updating if the database server name is changed.

  The data contained in lookup tables created in the Configurator can be stored in Microsoft Access tables instead if the following requirements are met:

  • An OLE DB driver is installed. Microsoft Office includes a 64-bit OLEDB driver named the Office System Driver that can be used to connect to Access, Excel, and text files. The provider name is Microsoft.ACE.OLEDB.<VersionNumber>.

    If Office is not installed, the driver is available as a separate download from the Microsoft Download Center by the name of Microsoft Access Database Engine Redistributable.

    For additional information, see Jet for Access, Excel and Txt on 64-bit systems at ConnectionStrings.com.

  • The ConnectionString registry setting is configured as described in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Server\UserDatabase

  • The TablesDb registry setting is configured as described in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Server

  • The WorkspaceDB registry setting is configured as described in HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Client

  Note:

  Depending on how much additional data is stored in Microsoft Access (for example: document subscriptions, audit log), the database can grow to where performance is degraded considerably. For that reason, we do not recommend using Microsoft Access for more than external lookup tables, the user account database, and local workspace data. Store all additional data in SQL Server instead.

• One of the Internet Information Services versions listed in Web Servers and Browsers. The minimum IIS components that must be installed for proper operation are described in Server Role Requirements.

  • If the Request Filtering feature option Allow unlisted file name extensions is disabled in IIS Manager, the following file extensions must be added to the File Name Extensions list and allowed: .dll,.gif,.png,.js,.css.

  • If Meridian Mobile will be deployed, additional requirements must be met as described in Install the Meridian API Service.

  • Transport Layer Security (TLS) 1.2 is supported by Meridian 2018 R2 Update 1 and higher.

• One of the web browsers listed in Web Servers and Browsers.