2.2. Default Server, Agent, and Storage Node Ports

As with other servers and services, JBoss ON servers and agents communicate with each other by connecting over system ports. JBoss ON uses ports for several different types of connections:
Server to database communication
The server has to be able to connect to its database. The database port number depends on both the type of database and the specific configuration for the database.
Server to agent communication
The server connects to an agent over a single port configured for the agent. This port is used for both standard and SSL communications between the server and agent.
Agent to server communication
An agent can talk to multiple JBoss ON servers, even if they use the same port (since each server is on a different host.) The agent will use either a standard port or an SSL port to connect to the JBoss ON server, depending on the connection (transport) method that is configured. The agent will only attempt to use a single port.
Server to storage node communication
The JBoss ON server receives the monitoring data from an agent, and it then forwards that information to an available storage node. THe server connects to the storage node over its client (CQL) port.
Storage node to storage node communication
For data integrity and availability, the monitoring data are regularly synchronized between the storage nodes. The nodes send data to one another over a communal cluster port, called a gossip port.
Note
Servers do not talk to one another directly, so there are no ports for server-to-server links.
The default port numbers for JBoss ON connections are listed in Table 2.4, “Default Ports”. The port numbers can be changed for any of the JBoss ON services or different values can be used at installation.

Table 2.4. Default Ports

Connection Type Port Number
Server to agent 16163
Agent to server (standard) 7080
Agent to server (secure) 7443
Server to database 5432 (default PostgreSQL port)
Server to storage node 9142
Storage node to storage node 7100