8.8. Overview of Client-Web Server Communications

Engineering Knowledge Manager

Installation Guide | Chapter 8: Installing a Front-End Web Server |

8.7.1. Apache |  | 8.8.1. SSL/TLS Certificates: Background
Prev |  | Next

## 8.8. Overview of Client-Web Server Communications

As shown in Figure 8.2: EKM with Front-End Web Server/HTTPS (DMZ Deployment), communications between the client browser and web server can either be unencrypted (HTTP) or encrypted (HTTPS). In order to support encrypted connections, the web server must possess a signed Secure Sockets Layer (SSL)/TLS certificate (commonly referred to as a cert), and be configured to enable encrypted connections over HTTPS.

Communications between the web server and the application server(s) on the EKM cluster node(s) via the load balancer are not encrypted when using the AJP or HTTP protocols. If encryption is required between the web server and the application server, then the load balancer should be configured to use the HTTPS protocol. Consult the JBoss and mod_proxy documentation for instructions on setting up mod_proxy for HTTPS.

Figure 8.2: EKM with Front-End Web Server/HTTPS (DMZ Deployment) shows a typical deployment of EKM using SSL/TLS in an internet-facing scenario.

Figure 8.2: EKM with Front-End Web Server/HTTPS (DMZ Deployment)

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.