15.2. Appendix B: Network Ports

Engineering Knowledge Manager

Installation Guide | Chapter 15: Appendices |

15.1. Appendix A: Setting Environment Variables for EKM |  | 15.3. Appendix C: Email Configuration
Prev |  | Next

## 15.2. Appendix B: Network Ports

Client to EKM Server Communication:

The web client communicates with EKM servers over certain network ports, which can differ depending on how EKM is set up and configured. Typical network ports used by the web client to communicate with EKM servers are given in the table below. If you are accessing EKM through a firewall, these ports must be allowed between the web client and the EKM server.

Table 15.1: EKM Server Network Ports for Web Client Communication

Port/Protocol | Used By
80/TCP | HTTP port (front-end web server)
443/TCP | HTTPS port (front-end web server)
8080/TCP[a] | HTTP port (JBoss application server)
8443/TCP[a] | HTTPS port (JBoss application server)
[a] This port number is subject to change according to the JBoss port offset used. See Appendix D: Resolving Network Port Conflicts.

Front-End Web Server to EKM Server Communications

EKM servers can be configured to use a front-end web server. Communication between a front-end web server and EKM server happens using the AJP, HTTP or HTTPS protocols, depending on the configuration of the front-end web server and EKM server.

In a scenario where the front-end web server is on a different network than the EKM server, and those networks are separated by a firewall, the firewall must allow the traffic to pass between the front-end web server and the EKM server. This scenario is typical when setting up EKM in an internet-facing deployment, where the front-end web server is on a DMZ network, and the EKM server is on an internal network. The traffic that needs to be allowed between the front-end web server and the EKM server is listed in the table below:

Table 15.2: EKM Server Network Ports for Front-End Web Server Communication

Port/Protocol | Used By
8019/TCP*[a] or 8080/TCP*[a] or 8443/TCP*[a] | mod_cluster (AJP) / JBoss (unencrypted) mod_cluster (HTTP) / JBoss (unencrypted) mod_cluster (HTTPS) / JBoss (encrypted)
[a] This port number is subject to change according to the JBoss port offset used. See Appendix D: Resolving Network Port Conflicts.

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.