Remote Site Caches

Because Meridian Enterprise is a centralized system, optimizing performance for remote users with modest available bandwidth can be a challenge, particularly if the users work with large files or many external references. Meridian Enterprise provides a variety of features to help meet this challenge, including Remote and Online modes for Power Desktop users and Remote mode for PowerWeb and Explorer users.

If a group of Meridian Enterprise users works in proximity to a corporate web server that is geographically closer to them than the Meridian Enterprise application server, Meridian Enterprise web server, or Meridian Explorer server, a site cache component can be installed and configured on their local web server. Site cache servers support Meridian Explorer clients and the Online and Remote modes of PowerWeb (HTTP or HTTPS) but do not support Offline mode or the Administration Console client (DCOM). They also support simultaneous connections from multiple sessions by the same user and simultaneous connections to multiple Meridian Enterprise servers.

The site cache temporarily stores documents (source or renditions) that the users work with so that they do not have to download them from the central server every time. The system response and performance to download and upload documents is greatly improved, comparable to users that are located near to a Meridian Enterprise server. The site cache service automatically synchronizes the cache with the Meridian Enterprise servers transparently in the background. Old and orphaned documents are removed from the cache (and from local workspaces) to make space for newer and active documents. Multiple site caches can be configured to serve separate groups of users that each have a local web server.

Note:

New documents created by remote users are sent immediately to the Meridian Enterprise web server and stored in the vault. Copies of the documents are added to the local site cache for future access.

Configuring a site cache server involves tasks on several servers as well as on the Meridian Explorer clients. The installation tasks are listed in the order in which they should be performed in the following table and are described in this guide and in other guides. Use the hyperlinks in the following checklist to find the instructions for each task. Track your installation progress by printing this checklist and placing a checkmark in the box in the Completed column as you finish each task.

Site cache configuration checklist
Completed Task Topic Reference

 

If using HTTPS, Install the site cache server certificate on the Meridian Enterprise Server machine.

When using HTTPS, it is now mandatory to install a site cache server certificate on the Meridian Enterprise Server machine for each site cache server, otherwise the site cache server is marked as invalid and an error like this one is shown in the BC Application Events:

Site Cache Server 'https://<pcname>/BCSiteCache' is unavailable due to these reasons:

  • One or more errors occurred.
  • An error occurred while sending the request.
  • The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
  • The remote certificate is invalid according to the validation procedure.
Note:

To provide preload tasks with a way to query site cache servers using HTTPS, ensure site cache servers have a self-signed certificate issued to localhost.

 

The Meridian Enterprise EDM Server service, Meridian Enterprise web application identity, Meridian Enterprise Server service, and the BCSiteCache web application identity must all run under the same account. Enter an appropriate domain account during Meridian Enterprise server installation when prompted. Confirm that the account is used by each of the services. For account requirements, see Granting domain privileges with a service account.

 

Integrate Meridian Enterprise with Meridian Enterprise Server and specify the correct HOST and UPN parameters for the Meridian Enterprise Server account.

Configuring the connection to Meridian Enterprise Server

 

Publish the vault that contains the documents to be cached as a PowerWeb location on only one Meridian Enterprise web server.

Creating a PowerWeb location

 

Confirm that the site cache server meets or exceeds the minimum system requirements.

Site cache server requirements

 

Disable Compatibility view of the BCSiteCache URL in Internet Explorer on the PC that will be used to configure the site cache server. Compatibility View on the MSDN website.

 

Register the site cache server in Meridian Enterprise Server.

Register site cache servers

 

Configure the site cache server in Meridian Enterprise Server.

Configure site cache servers

 

Pre-load the site cache with documents. Pre-load site caches

 

On the client PCs, confirm that the local workspace component of Meridian Enterprise Application Integration is installed and running (BlueCieloECM.SiteCache.LwsClient.exe).  

 

On the client PCs, confirm that Meridian Enterprise Application Integration is set to Remote mode.

Work offline or remote

 

On the client PCs, confirm that the site cache URL is set correctly.

Configure local workspace

HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Client

 

If users will connect from a different domain or if the site cache server is behind a proxy server, advise users how to set the connection settings of the site cache client.

Configure a Site Cache Connection

 

On the client PCs, confirm that the local workspace option Use in Offline and Remote modes is enabled.

Configure Local Workspace

 

On the client PCs, if they will be used in Remote mode with application links and large assemblies, consider enabling the EnableRemoteDocumentCache setting.

HKEY_CURRENT_USER\Software\Cyco\AutoManager Meridian\CurrentVersion\AMLink\Settings

2021 R2