This document describes how to download and install the RTView DataServer for Infrastructure for use with Enterprise Monitor, how to configure the data server including defining the connection information for the Solution Package for Infra, how to add alert and historian database connections, how to add connections to Enterprise Monitor, and how to verify that your setup is working properly in Enterprise Monitor.
Note: In addition to using the RTView Configuration Application for configuring your connections, you can use the Property Editor REST API to import initial connections or automate connection updates. See Property Editor REST API for more information.
Before You Get Started
You must have Java installed and you should know the installation directory path.
You should know the correct full path to the directory containing the jar files for each of your solution packages.
You should know the connection settings for your solution packages:
Amazon Web Services connections: Location of your .jar files, the Access ID Key, the Secret Access Key, and the fully qualified name for an Amazon Service (Cloudwatch) that provides monitoring data.
Docker connections: Verify cAdvisor is set up properly and know the desired port to use if different from the default port.
Microsoft SQL Server connections: Connection name, URL for the SQL server, and username/password (if specified).
MongoDB connections: Connection name and URL to each MongoDB to which you want to connect.
MySQL connections: Connection name, database URL, and username/password (if specified).
Node.js connections: Know the desired port to use if different from the default port.
RTView Host Agent connections: All configurations are optional.
RTView Manager connections: Connection name, host name/IP address of the MBean server, port exposed by your MBean server, and username/password (if specified).
RedHat JBoss connections: Connection name, URL for the connection, and username/password used for the connection (if specified).
VMWare connections: Connection name, connection method (vCenter Server or Direct EXSi Host), URL for the connect method, and username/password (if specified).
If you are upgrading to a new version of the DataServer, review theGeneral Upgrade Stepsdocument to see if there are any additional steps required.
Downloading the RTView DataServer for Infrastructure
Open a browser and navigate tohttps://sl.flexnetoperations.com.
Login using your RTView Download Center account login/password.
If you do not have an RTView Download Center account, contact firstname.lastname@example.org about helping you to create an account.
The RTView Download Center page displays.
Click the SL Corporation link in the Browse My Software and Documentation region.
The list of available Product Lines displays.
Click RTView DataServer for Infrastructure.
The Product Information page displays.
Click RTView DataServer for Infrastructure.
The Product Download page displays.
Click theRTViewDataServerInfra_<version>.zipfile or, if you want to download multiple files, select the check box next to the different deliverables and click the Download Selected Files button.
The compressed file(s) is/are saved to your machine.
When you install the DataServer, a temporary license key is included. SL Corporation will send you a permanent key that you will need to add to your RTView license key file so that you can extend the operation of your monitoring system.
This is a universal key that will enable you to run RTView on different machines and platforms. It is your responsibility to ensure you use RTView within the terms of your End User License Agreement (EULA).
To update your RTView system with your new license key, open a command window and:
Navigate to RTViewDataServerInfra/rtvapm/rtview/lib.
Edit the KEYS file using a text editor.
Copy/paste the new replacement key to the file.
Save the KEYS file.
Installing and Starting the RTView DataServer for Infrastructure
Note: If using UNIX, do not include spaces in your installation directory path. The start_server.sh and stop_server.sh scripts will not function properly if spaces are included in the installation directory path.
Extract All (Windows)/unzip (UNIX/Linux) the file to the directory of your choice. For UNIX/Linux, useunzip -ato unzip the file.
Open a command window and set theJAVA_HOMEenvironment variable to point to your Java Installation. For example:
set JAVA_HOME=C:\Program Files (x86)\Java\jre1.8.0_201(Windows)
Or, in Windows, you can set JAVA_HOME as an environment variable (in Control Panel > System > Advanced system settings), where it will then be used by all command windows and when you double-click on a .bat file.
In the command window, navigate to theRTViewDataServerInfradirectory and type:
Or, in Windows, you can double-click on the start_server.bat file.
Note: This script starts the Data Server on port 3278 with HTML Server (Eclipse Jetty, by default) on port 3270. If these ports conflict with other processes running on your system, you can change the first two digits of the ports by using-portprefix:and specifying the first two digits you want to use for the ports in the command line. For example:start_server.bat -portprefix:44(which would change the ports to 4478 for the Data Server and 4470 for HTML Server). If you want to save your port prefix, you can change the port prefix in the RTView Configuration Application (see the next section), or you can use -saveportprefix: command line argument (for example: start_server.bat -portprefix:44 -saveportprefix).
Configuring the Data Server
Next, you need to create your connections for each of your solution packages using the RTView Configuration Application.
Open a browser and type:
http://localhost:3270/rtvadmin (for a local installation using Eclipse Jetty)
http://<IP address>:3270/rtvadmin (for a remote installation using Eclipse Jetty)
Note: If you specified a different port at startup (due to a port conflict), you must use the port you specified in the command line. For example, if you specified44as your port prefix in the command line at startup, then you would use:
TheAuthentication requireddialog displays.
Log in using rtvadmin/rtvadmin as the username/password.
The RTView Configuration Application displays.
Click RTView DataServer for Infra.
The RTView Configuration Application displays with the Generaltab open.
As previously mentioned, if you modified the port at startup, you should modify the port prefix so that you do not need to specify the port on the command line every time you run the startup script. To do so, navigate toServer Configuration>General>GeneralTab >Ports>Port Prefixand define a new port prefix. If you change thePort Prefixto44then, after saving your changes and restarting your data server, you would access the RTView Configuration Application for the RTView DataServer for Infrastructure using the following URL: http(s)://localhost:4470/rtvadmin(instead of the default http(s)://localhost:3270/rtvadminURL)
Under Solution Package Configuration, select the desired solution package you want to configure and click the link below to view the steps required to set up the configuration for the solution package:
Next, you need to connect your data server to Enterprise Monitor. To do so:
ClickServer Configuration>EM Integration.
TheEM INTEGRATIONtab displays.
Click theIntegrate with Enterprise Monitortoggle.
Note: This field can be enabled by default by setting theRTVDS_INTEGRATEENABLEDenvironment variable to 1 (for example: RTVDS_INTEGRATEENABLED=1).
TheCentral Server URLfield and associatedAnnounce this RTView Data Server to the Central Servertoggle display.
Specify theCentral Server URLto be used to connect to your RTView Central Server. By default, a local connection is defined (localhost:10018) and does not need to be modified if your Central Server and Data Server are on the same machine. If they are on different machines, enter the URL containing the IP address and the port like so:
Note: You can specify a different default for the Central Server URLfield by specifying theRTVDS_CENTRALURLenvironment variable (for example: RTVDS_CENTRALURL=http://localhost:10070/rtview-central-rtvdata).
Click the Announce this RTView Data Server to the Central Server toggle to automatically connect the data server to RTView Central.
Note: This field can be enabled by default by setting the RTVDS_ANNUNCIATEENABLEDenvironment variable to 1 (for example: RTVDS_ANNUNCIATEENABLED=1).
The following fields display:
RTView Data Server Name: Define the name of the data server that you want to display in Enterprise Monitor. Modifying the default name in this field is optional. However, for our example, enterInfra_Data_Serverso that we can verify our change in our verification section later in this document. This field can be defined by default by defining the RTVDS_NAME environment variable (for example: RTVDS_NAME=INFRAMON_LOCAL). Note: You can only enter alphanumeric characters, underbars, and dashes in the data server name.
RTView Data Server URL: The URL that the Central Server should use for connecting to this RTView Data Server. The default depends on theHTML Server Enabledoption on theData Servertab. If theHTML Server Enabledoption is selected, the default ishttp://hostname:3270/rtvdata. If disabled, the default ishostname:3278where 32 is the Port Prefix for this project and hostname is the RTView Server Host.This field can be defined by default by defining the RTVDS_URL environment variable (for example: RTVDS_URL=http://myhost:3270/rtvdata).
RTView Query URL: The URL that HTML clients should use to query this RTView Data Server. The default depends on theHTML Server Enabledoption on theData Servertab. If theHTML Server Enabled option is selected, the default ishttp://hostname:3270/rtvquerywhere 32 is the Port Prefix for this project and hostname is the RTView Server Host. IfHTML Server Enabledis disabled, this field is blank. IfHTML Server Enabledis disabled, this field is blank. This field can be defined by default by defining the RTVDS_QUERYURL environment variable (for example: RTVDS_QUERYURL=http://myhost:3270/rtvquery).
RTView Data Server Host: The Host name or IP address that the Central Server and html clients should use for connecting to this RTView Data Server. If not specified, the IP address for the host is used. This field can be defined by default by defining the RTVDS_HOST environment variable (for example: RTVDS_HOST=localhost).
CITypes to Exclude: The CI Types, if any, that you want to exclude from the Service Model in the Central Server. If not specified, all CI Types for the configured solution packages are included in the Service Model. To select the CI Types you want to exclude, click the associated button to display theCI Types to Excludedialog, select the desired CI Types, and clickOK. This field can be defined by default by defining the RTVDS_CITYPESTOEXCLUDE environment variable (for example: RTVDS_CITYPESTOEXCLUDE=DOCKER-CONTAINER,DOCKER-ENGINE).
Saving Your Changes and Restarting the Data Server
Once you have created all of your connections, click theSAVE button in the RTView Configuration Application.
For your changes to go into effect, you must stop and restart the data server by either:
clicking thebutton (in the upper right-hand corner of the window)...
or by typing the following in your installation directory in the command window:
Verifying Your Setup
To verify your setup:
Open a browser, access the RTView Configuration Application for RTView Central Servers (Enterprise Monitor) using http://localhost:10070/rtview-central-rtvadmin, and log in using rtvadmin/rtvadmin as the username/password.
Your data server (Infra_Data_Server, for our example) displays in the list belowRTView Central Servers. You can edit your data server connections/configurations in the RTView Configuration Application for RTView Central (http://localhost:10070/rtview-central-rtvadmin) or in the RTView Configuration Application for the RTView DataServer for Infra deliverable (http://localhost:3270/rtvadmin).
Open a browser, access Enterprise Monitor (for example, http://localhost:10070/rtview-central-classic), and log in using admin/admin as the username/password.
Click Admin > Architecture > System Overview and check to make sure that your newly connected data server (Infra_Data_Serverin our example) displays in the Data Servers region and that CI Metrics are being collected.
You can also check the incoming data in your caches by opening a browser and accessing the following URL:
http(s)://localhost:3270/common (for a local installation using Eclipse Jetty)
http(s)://<IP address>:3270/common (for a remote installation using Eclipse Jetty)
The RTView Cache Viewer application displays, which allows you to view the details for the caches that are collecting data.