DTS uses a number of communication paradigms to pass information between various modules as well as to and from external actors:
•The Internal Communication Bus (ICB) is the main communication channel of the system. Most of the first-party modules communicate using this bus, and it can also be used by third party clients that adhere to the API. In actuality, it represents a standard Redis server.
•Mongo API over TCP/IP is used by all the modules which need to access the Projects Repository to perform the necessary operations.
•HTTP is used by the GUI Front-End to communicate to the GUI Back-End.
•SMTP is used between the GUI Controller and the Customer Mail Server.
•SSH/SCP is used by the GUI Controller to directly deploy web services into certain Application Servers and by the Agent to control the deployment cluster remotely.
•Other APIs are used by the various Connectors to access the specific datasources (e.g. ojdbc, ACPT, etc.). These generally also function over TCP/IP.
Ports
DTS deployments can vary depending on network topology, resources and usage. However, certain functions will always require remote access on configured ports.
The required ports are:
•The GUI Webapp port (configurable) must be opened to allow remote users to interact with the web GUI.
•The ICB (Redis) port (configurable) must be opened to allow remote clients to access the system.
•The SSH port (22) must be opened to allow installation and maintenance operations.
For more information on deployment models and specific ports, please see Deployment.