2.1.2. Setting Up Caching

If you want to use caching in a globally distributed environment, you must create a Cache Server definition in the EKM server that hosts the repository that remote users will be uploading files to/downloading files from. A Cache Server definition indicates the host name of the EKM server that will cache the data. Referring to Figure 2.3: Distributed Setup with Dedicated Cache Server, a Cache Server definition would need to be specified in the Master Server in New York in order to establish caching on the server in London. See Creating a New EKM Cache Server.

When creating the Cache Server definition, you will specify which remote EKM users will use it. You may also assign a Cache Server to a user when setting up or modifying their user account (refer to Adding a New User). Referring once again to Figure 2.3: Distributed Setup with Dedicated Cache Server, when the administrator in New York creates a Cache Server definition on the Master Server for the Cache Server in London, they will assign users based in London to the Cache Server definition. Users based in New York would not be assigned to the Cache Server because they are already accessing the data locally on the New York server. When a user in London (who is part of the Cache Server definition) logs into the Master Server in New York, the Master Server will know to involve the Cache Server in London when files are being transferred to/from the Master Server.


Note:  When transferring files using the File Transfer Client, if a connection to the cache server cannot be established or is lost, files will instead be transferred to/from the EKM repository directly.

This behavior will be captured in the following logs:

  • Windows: %APPDATA%\Ansys\v182\EKM\connector.log

  • Linux: ~/.ansys/v182/EKM/connector.log



Release 18.2 - © ANSYS, Inc. All rights reserved.