HTML UI
This interface is implemented in HTML and is deployed as a servlet, rtview-central.war, which is configured by default to use HTTP authentication. Browser clients connect via HTTP or HTTPS depending on the RTView© Enterprise User's Guide Version 6.4.2 configuration. For secure deployments, it should be configured to use HTTPS since HTTP authentication does not encrypt user credentials.
The HTML UI sends data requests to the rtview-central-rtvquery.war servlet that connects to the Central Server via socket. By default, this socket is unsecured, but the rtview-central-rtvquery.war servlet will connect to the Central Server via secure socket if the Central Server is configured for SSL sockets.
By default, the rtview-central-rtvquery servlet is not configured for authentication, but can be modified to require HTTP authentication by doing the following:
| 1. | cd to rtvapm and run rtvapm_init. |
| 2. | cd to projects\rtview-server. |
| 3. | Run update_wars.bat (or .sh) -secure. |
| 4. | Deploy the generated war files to your Application Server. |
Note: Jetty does not support secured rtvquery servlets. You will need to use Tomcat or another Application Server.
Additionally, the HTML UI will connect to each RTViewDataServer via the rtvquery servlet for that Data Server as configured in the EM Integration tab in the Configuration Application in the RTViewDataServer. By default, the EM Integration tab uses the rtvquery servlet that is hosted in Jetty. However, for final deployment, it is recommended that you deploy all of RTViewDataServer servlets to the Tomcat that is included with RTViewCentral. There are two reasons for this. First, all Enterprise Monitor browser clients that use the HTML UI need permission to access the rtvquery servlet for each RTViewDataServer. If you use the Jetty server, this means that port XX70 on each host running the RTViewDataServer needs to be accessible to all browser clients (where XX is the port prefix for the RTViewDataServer). If you use the RTViewCentral Tomcat, only that host and the Tomcat port need to be accessible. Second, if the rtvquery servlets for the RTViewDataServers are configured for HTTP authentication, additional setup is required if they are not hosted on the same Application Server Security as the Central HTML UI.