PTC Arbortext Content Delivery Deployment > Planning Your Deployment > Communication Protocols
  
Communication Protocols
PTC Arbortext Content Delivery leverages web-based protocols for communication with clients. These protocols are primarily HTTP(S) over standard web ports.
Server-to-server and application-to-application communication leverages a broader number of protocols and ports. The table that follows lists the protocols and communication paths used within the PTC Arbortext Content Delivery architecture.
Software Component
Default Port
Protocol
Client to PTC Arbortext Content Delivery Application
8080
HTTP
PTC Arbortext Content Delivery to Core Server
2020
CORBA
PTC Arbortext Content Delivery to Core Server (applicable in case of cluster or multisite environment)
2021
CORBA
PTC Arbortext Content Delivery to Core Server (applicable in case of cluster or multisite environment)
2022
CORBA
PTC Arbortext Content Delivery to Core CMI Server
2010
CORBA
PTC Arbortext Content Delivery Application to LDAP
1389
JNDI
PTC Arbortext Content Delivery Application to Database
1521
JDBC
PTC Arbortext Content Delivery intra-server communication
8443
HTTPS
PTC Arbortext Content Delivery License Server
7790
TCP
PTC Arbortext Content Delivery MongoDB Listener
27017
JDBC
PTC Arbortext Content Delivery Load Balancer port
2000
CORBA
* 
In case of cluster or multisite environment with more than two cores, other ports (2023, 2024, and so on) need to be open.
In the case of the license server, if you do not set a port for ptc_e vendor daemon, a port is assigned automatically every time you start the license server.
For more details, see the “Troubleshooting” section in Installing a Stand Alone License Server.