This document describes how to download and install the RTView DataServer for Kafka for use with Enterprise Monitor, how to configure the data server including defining the connection information for the Solution Package for Kafka, 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 Apache Kafka jar files.
You should know the settings for your Zookeeper connections: Client Port, Host, JMX Port, Username/Password, and Cluster Name.
You should know the settings for your Broker connections: Client Port, Host, JMX Port, Username/Password, Cluster Name, and Topic Names.
You should know the settings for your Producer connections: Host, JMX Port, Username/Password, and Cluster Name.
You should know the settings for your Consumer connections: Host, JMX Port, Username/Password, Cluster Name, and Client-ID*.
* For RTView to correctly associate the consumer JMX metrics with the other consumer metrics (for example, consumer lag), the connection name and the client ID need to be the same. So, you can either assign a connection name and use that name when you start your consumer process, or you can use the client ID (that is already running) as the connection name when adding connections.
If you are upgrading to a new version of the DataServer, review the Upgrade Steps document to see if there are any additional steps required.
Downloading the RTView DataServer for Kafka
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 email@example.com 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 Kafka.
The Product Information page displays.
Click RTView DataServer for Kafka.
The Product Download page displays.
Click theRTViewDataServerKafka_<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 RTViewDataServerKafka/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 Kafka
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 (inControl 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 theRTViewDataServerKafkadirectory and type:
In Windows, you can double-click onstart_server (Windows Batch File) in theRTViewDataServerKafkadirectory.
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 DataServer
Next, you need to specify the directory path to your Apache Kafka .jar files and you need to create your connections using the RTView Configuration Application.
Open a browser and type:
TheAuthentication requireddialog displays.
Log in using rtvadmin/rtvadmin as the username/password.
The RTView Configuration Application displays.
ClickRTView DataServer for Kafka.
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.
The EM INTEGRATION tab 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).
The following fields display:
Central Server Connection: Specify the URL to be used to connect to your RTView Enterprise Monitor 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 IP address and port like so:
Note: You can specify a different default for the Central Server Connection field by specifying the RTVDS_CENTRALURL environment variable (for example: RTVDS_CENTRALURL=RTViewCentralHost:10018.
RTView Data Server Connection: Specify the URL that the RTView Enterprise Monitor Central Server should use for connecting to this RTView Data Server. The default value is the internal IP address. If the Central Server cannot access the internal IP address, then you must modify this value to use the external IP address. This field can be defined by default by defining the RTVDS_URL environment variable (for example: RTVDS_URL=myhost:3278).
RTView Data Server Query URL: Specify the URL that the RTView Central Server HTML user interface should use to query data from this RTView Data Server. The default value uses the internal IP address. If all browser clients cannot access the internal IP address for this system, you must change this value to use the external IP address or deploy the rtvquery servlet to an application server on an accessible system and you should specify that value in this field. 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 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, enter Kafka_Data_Server so 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=KAFKAMON_LOCAL). Note: You can only use alphanumeric characters, underbars, and dashes when naming the data server.
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 the CI Types to Exclude dialog, select the desired CI Types, and click OK. This field can be defined by default by defining the RTVDS_CITYPESTOEXCLUDE environment variable (for example: RTVDS_CITYPESTOEXCLUDE=KAFKA-BROKER,KAFKA-CONSUMER).
Send Connection Information To Enterprise Monitor: By default, the associated Announce this RTView Data Server to the Central Server toggle is selected, which will automatically connect the data server to RTView Central. If you do not want to automatically connect the data server to RTView Central, deselect this toggle. If deselected, you must define the connection from RTView Central to this data server in the RTView Central Configuration Application.
Note: This field can be enabled by default by setting the RTVDS_ANNUNCIATEENABLED environment variable to 1 (for example: RTVDS_ANNUNCIATEENABLED=1).
Saving and Restarting Your Changes
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 dataserver from your installation directory by typing the following in your command window:
Click thebutton in the upper right-hand corner.
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 (Kafka_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 Kafka 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 (Kafka_Data_Serverin our example) displays in the Data Servers region and that CI Metrics are being collected.
Once you have set up your connections for your data server, you can verify your setup by accessing the following URL:
The RTView Cache Viewer application displays, which allows you to view the details for the caches that are collecting data.