2.1. Deployment Options

Engineering Knowledge Manager

Installation Guide | Chapter 2: Overview of an EKM Server Installation |

Chapter 2: Overview of an EKM Server Installation |  | 2.2. How an EKM Server is Configured
Prev |  | Next

## 2.1. Deployment Options

EKM servers can be deployed to serve any number of users. Each EKM server can be deployed in a single-node or multi-node configuration, on one or more server hosts. Multiple EKM servers can be deployed in a distributed fashion to serve large numbers of users in geographically separate locations.

The simplest scenario is to deploy EKM as a single-node server on a single host, where all services (cluster database server, cluster node, and cluster file server) are on the same host.

More complex and powerful configurations are possible by separating services onto different hosts, such as configuring EKM to access a cluster database server and cluster file server on other hosts. Additionally, the EKM server itself may be deployed as a multi-node server, where multiple cluster nodes work together to act as a single EKM server capable of handling more user requests. A front-end web server is typically employed to provide load-balancing and a single point of access to an EKM server, whether the EKM server is single-node or multi-node.

Additionally, you can configure a shared EKM server to use an external authentication service such as LDAP or Windows Active Directory or to use Windows/Linux OS-based authentication to simplify management and reduce the number of passwords users need to keep track of. See Configuring Login Authentication and Access Settings for more details.

Multiple EKM servers can be combined in a distributed deployment to serve users in geographically separate locations. In a distributed deployment, EKM servers in each location serve local users, and provide distributed file caching for data residing in other locations. See Distributed Servers and Workspace Access.

In a distributed deployment, each EKM server can also be configured to run jobs in each location while sharing one common, centrally-stored set of data. This is accomplished by setting up Master and Slave workspaces, where the Master contains the central EKM repository, and the Slaves are used for running jobs. See Running Jobs in a Distributed Environment.

Some of the components of an EKM server deployment are configured manually, and others are set up automatically during EKM server setup. Advanced configurations provide higher performance and availability, but require advanced IT experience to configure and administer. The ANSYS Worldwide EKM Enterprise Team can help you plan and execute a successful EKM deployment that takes advantage of EKM’s flexible deployment options to meet your organization’s needs now and in the future.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

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