Chapter 2: Overview of Servers and Workspaces

EKM provides many ways to structure your information and manage multiple workgroups that are spread across multiple locations. Two concepts are defined in EKM for this purpose:

Every EKM server contains one default user-accessible workspace with a repository for data. More workspaces can be created if needed. When you set up a workspace you determine who can access it, and specify the permissions that each user has in that workspace. Every EKM server also has a hidden workspace for caching data from remote servers. This workspace may be involved in file transfers when data is downloaded from or uploaded to a remote EKM server using the File Transfer Client.

Figure 2.1:  Default Composition of an EKM Server

Default Composition of an EKM Server

Planning Server Installations

A single EKM server is sufficient if all users are located close to each other in the same region. But if a substantial number of users are accessing EKM from remote offices over a WAN and the connection speed between the offices is significantly impacting the data transfer rate, then multiple EKM servers can be installed (see Figure 2.2: Multiple EKM Servers in a Global Setup). The recommended architecture in this case is to use a “master” server, that will contain globally shared data, and to have a number of regional servers. You could have one regional server for each remote office or share a regional server with several closely located remote offices. Regional servers provide the following benefits:

A detailed overview of regional servers and how they can be used for caching is provided in Distributed Servers and Workspace Access.

How Workspaces are Used

Workspaces are primarily used as independent data partitions that can be configured independently of each other and that contain their own set of users and groups. Data from one workspace is not visible to, and cannot be accessed from, another workspace. This way, workspaces can be viewed as independent islands of data. Each server will have at least one production workspace that contains the primary data and user accounts, but additional workspaces can be created as explained in Creating and Managing Workspaces. Some of the reasons for creating additional workspaces are highlighted below:

In general, workspaces should not be used as a security mechanism to provide different groups in a company with their own private space. Data isolation can be achieved in a single workspace through the use of groups, per-user access level assignments, and object-level permissions. Multiple workspaces increase management overhead and impede the sharing of data between users and groups belonging to different workspaces. Even if data sharing is not a short-term requirement, it may become an issue in the long term.


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