Central Server

The Central Server connects to one or more RTViewDataServers via socket or via the rtvdata servlet for that Data Server to collect metric and alert data for the service model. The Central Server serves service model and alert data to the RTView Enterprise HTML UI via the rtview-central-rtvquery.war servlet that connects via socket on port 10018.

The Historian runs in the same directory as the Central Server. Each RTViewDataServer also connects to the Central Server via port 10078 or via the rtview-central-rtvdata.war servlet in order to query alert thresholds. By default, socket connections to the Central Server are unsecured. The Central Server supports secure socket connections (SSL) without certificates. After the Central Server is configured for secure sockets, the Historian, RTViewDataServers, and all rtvdata and rtvquery servlets will connect via secure socket.

The Central Server will connect to each integrated RTViewDataServer via socket or rtvdata servlet as configured in the Configuration Application EM Integration page for that RTViewDataServer.

The Central Server HTML UI will connect to the Data Server via the rtvquery servlet as configured in Configuration Application EM Integration page for that RTViewDataServer. By default, it connects to the rtvquery servlet that is hosted in Jetty. This means that all RTView Enterprise Monitor browser clients that use the HTML UI need permission to access port XX70 on the host running the RTViewDataServer (where XX is the port prefix for the RTViewDataServer). If this is not desirable, configure and run update_wars in the projects/rtview-server directory and deploy the war files to the Tomcat installation included with the Central Server. With this deployment, only the system where RTView Enterprise Monitor is installed will need permission to access the host running the RTViewDataServer. After deploying your servlets to Tomcat, modify the connections in the Configuration Application EM Integration page to point to the servlets in Tomcat.

The Configuration Application connects to the Central Server via the rtvadmin servlet to read and write properties files. The rtvadmin servlet connects to the Central Server via socket on port 10078. See the Configuration Application for information about servlet authentication. The rtvadmin servlet will connect via secure socket if the Central Server is configured for SSL sockets.

If the Historian is enabled, the Central Server connects to the RTVHISTORY database on startup to read initial cache history data and if RTView Enterprise Monitor or RTVCloud displays request history data older than the in-memory cache history.

The Central Server opens a JMX port on 10013 to enable monitoring. By default, the JMX port is not secured, but can be secured via SSL and username/password.

The Central Server also runs an internal Jetty application server that hosts its servlets on port 10070. It also hosts a simple cache viewer at http://localhost:10070/common. See the RTView© Enterprise User's Guide Version 6.4.2 section for information on disabling or securing Jetty.

The Data Server optionally executes alert notifications based on user settings. Since the notification actions are user defined, security must be determined by the user.