Previous Topic: Ports Used by Database ServersNext Topic: Maintain the Orchestrator DNS Name or IP Address


Ports Used by Web Clients

The following table provides an overview of the ports used for communications from the Web clients.

Communication from Web Clients

From

Port

To

Default Listening Port

Protocol

Configuration

Description

Web Browser (CA EEM Administrator)

Any

CA EEM

5250

TCP

CA EEM configuration

Web Browser accessing the CA EEM UI.

Web Browser (CA Process Automation Web UI user)

Any

Load Balancer

80

TCP

Apache: httpd.conf

NGINX: pam-server.conf

F5: iRules Config

Load Balancer port for basic communication

Web Browser (CA Process Automation Web UI user)

Any

Load Balancer

443

TCP

Apache: httpd.conf

NGINX: secure-pam-server.conf

F5: iRules

Load Balancer port for secure communication

Web Services (SOAP) client

Any

Load Balancer

80

TCP

Apache: httpd.conf

NGINX: pam-server.conf

F5: iRules Config

Load Balancer port for basic communication

Web Services (SOAP) client

Any

Load Balancer

443

TCP

Apache: httpd.conf

NGINX: secure-pam-server.conf

F5: iRules

Load Balancer port for secure communication

Catalyst REST client

Any

Load Balancer

7000

HTTP

Apache: httpd-proxy.conf

NGINX: pam-rest.conf

F5: iRules config

CA Process Automation Catalyst container port

Catalyst REST client

Any

Load Balancer

7443

HTTPS

Apache: httpd-proxy.conf

NGINX: pam-rest.conf

F5: iRules config

CA Process Automation Catalyst container secure port

Web Browser (CA Process Automation Web UI user)

Any

Orchestrator

8080

HTTP

OasisConfig.properties

Browser talks to Orchestrator on this port with basic communication.

Web Browser (CA Process Automation Web UI user)

Any

Orchestrator

8443

HTTPS

OasisConfig.properties

Browser talks to secure Orchestrators on this port.