Data Collector

The Data Collector process is optional and is used to distribute connections to Monitored Components instead of having the Data Server connect to each component to be monitored directly. This process collects data from Monitored Components and forwards it to the Data Server via socket on port 3272 or the rtvagent servlet.

In the RTView Configuration Application > Data Server > COLLECTOR tab, the Target definition determines whether data is sent to a socket or a servlet. If the URL for the target is host:port, then it will be sent via socket, which is not secured by default. This socket can be secured via SSL by specifying the following property on the CUSTOM PROPERTIES tab in the Configuration Application of each receiver Data Server:

Property Name: sl.rtview.rtvagent.ssl
Property Value: true
Property Filter: collector

If the url is the receiver's rtvagent servlet, it will send data to that rtvagent servlet, which will connect via socket to the Data Server on port 3272 that can be secured via SSL as described above.

While the rtvagent servlet cannot be configured for authentication, Tomcat access filters can be used to restrict access and it can be deployed on https. While the Data Collector typically does not have data clients, it accepts data requests via socket on port 3276 that can be secured as described in the Data Server section.

The Data Collector also opens jmx on port 3266 for monitoring. By default, the jmx port is not secured, but can be secured via SSL and username/password. See RTView© Enterprise User's Guide Version 6.4.2

Monitored Components

Monitored components consist of EMS Servers, Hawk MicroAgents, BW Servers, Solace Brokers, and so on. See Creating Secure Connections for more information on securing connections to the monitored components.