Servigistics InService Deployment > Planning Your Deployment > Communication Protocols
  
Communication Protocols
Servigistics InService 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 Servigistics InService architecture.
Software Component
Default Port
Protocol
Client to Servigistics InService Application
8080
HTTP
Servigistics InService to Core Server
2020
CORBA
Servigistics InService to Core CMI Server
2010
CORBA
Servigistics InService Application to LDAP
389
JNDI
Servigistics InService Application to Database
1521
JDBC
Servigistics InService intra-server communication
8443
HTTPS
Servigistics InService License Server
7790
TCP
Servigistics InService MongoDB Listener
27017
JDBC
* 
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.