A cache server is just an EKM server that has been set up to allow files to be accessed on a Local Area Network (LAN) while the actual EKM repository is accessed via a Wide Area Network (WAN). When a cache server is present, files that you want to upload to the EKM repository using the File Transfer Client are first uploaded to the cache server. The cache server then communicates with the EKM server and handles the transfer to the EKM repository. This can significantly improve transfer times because files are located locally. Figure 7.6: Example of Distributed EKM System with Cache Servers shows an example of a distributed EKM system with cache servers.
You can monitor a file transfer by looking at the Stage column in the File Transfer Client. As files are being uploaded to the cache server, the Stage reads Uploading files to cache. Once the files have been uploaded to the cache server, the cache server sends a request to EKM to upload the files to it. As files begin uploading to a temporary location in EKM, the Stage changes to Uploading files to EKM from cache. Next, files are written to the repository, and metadata and simulation details are extracted. During this stage the Stage reads Importing files to EKM. Once the files have been successfully written to the repository, the Stage will read Complete.
Note: If a connection to the cache server cannot be established or is lost, files will be transferred to/from the EKM repository directly.