Internal communication

In the following schema, you can see the communication paths between the different Collibra Data Intelligence Cloud components.

Note HTTPS is always used for Cloud environments. For on-premises environments, HTTPS is only used if you enable it.
The Agent and all services are all separate processes.

Communication path Description
  • Agent → Repository service
  • DGC service → Repository service
 Send SQL statements over JDBC, via port 4403.
Agent → DGC service Send management-specific commands with a private REST interface (JMX REST) over HTTP, via port 4400.

DGC service → Search service

Send search requests using the Transport protocol via port 4422.

Agent → Search service

Send management specific commands with a private REST interface over HTTP(S), via port 4421
Collibra clients → Collibra Data Intelligence Cloud Access to Collibra with the public REST interface (REST) over HTTPS.
  • Agent → Jobserver service
  • DGC service → Jobserver service
 Send job commands using a REST interface over HTTPS, via port 4404.

Jobserver service → DGC service

Poll the DGC service if there are any jobs to be executed. This uses the built-in reverse proxy servlet of the DGC service.

If this type of communication is set up, the DGC service does never initiate a communication to the Jobserver.

Jobserver service → Jobserver database

Send SQL statements over JDBC, via port 4414.
  • Agent → Monitoring service
  • Monitoring service → DGC service

Send job commands using a REST interface over HTTPS, via port 4407.

The monitoring service connects to the DGC service via port 4400.

Console → Console database

Send SQL statements over JDBC, via port 4420