Output Data to PubSub+ Monitor

To output monitoring data to PubSub+ Monitor, you Start and Login to the Solution Package for Solace and Configure Data Collection.

Proceed to Start and Login to the Solution Package for Solace.

Start and Login to the Solution Package for Solace

Navigate to the SolacePubSubMonitor/bin directory and execute the start_servers.sh script (or start_servers.bat for Windows).

Open a browser and go to:

Use rtvadmin/rtvadmin for username/password.

The Solution Package for Solace opens. The displays populate with data after you add connection properties for your Solace Message Brokers (which is subsequently described in these instructions).

Proceed to Open the RTView Configuration Application.

Open the RTView Configuration Application

Open a browser and go to:

Use rtvadmin/rtvadmin for username/password.

The RTView Configuration Application HOME page opens.

cui_solace_selectProject.gif

Select the Solace Monitor project.

The main configuration page for the RTView Server - Solace Monitor project opens.

The navigation tree is in the left panel and the General and Custom Properties tabs are shown in the upper part of the main page. The name of the selected tab is highlighted and the other tabs are grayed out. You click on either of the grayed tabs to change the selected tab.

cui_mainConfigPg.gif

These instructions use the following format to describe navigation to each tab: Navigation tree>Tab. For example, the figure above illustrates the General>GENERAL Tab.

Proceed to Configure Data Collection (a required configuration).

Configure Data Collection

This section describes how to define the connection for the brokers you wish to monitor and verify that data is collected from them. This configuration must be performed before running any deployment of the Monitor. This configuration is the only required configuration.

If you don’t have special requirements for running the monitor (such as running multiple data collectors in the same host), there is no need to cover the optional subsections. Consult Technical Support before modifying other configurations to avoid the circumstance of future upgrade issues.

Note that for Solace Cloud Event Brokers you will need the exact SEMP version on each of your Solace Cloud Brokers. See Obtain SEMP Version.

To define Solace Broker connections:

  1. Open the RTView Configuration Application, select Solace (in navigation tree)>CONNECTIONS tab and click ConfigUI_Connections_Add_button.gif.

    cui_solace_connects.gif
  2. The Add Connection dialog opens.

    cui_solace_addConnect.gif
  3. In the Add Connection dialog do the following:

  4. Repeat these steps to add more brokers and when finished, click cui_solace_AddconnSAVEbutton.gif to close the dialog and cui_save_button.gif (in title bar) to save your settings.

  5. The connections you created are listed in the Connections tab. For HA pairs, the connection string for the backup broker has "-B" concatenated to it.

  6. Click cui_requires_restart.gif to apply changes. The data server will be available again in 10-15 seconds.

  7. Open a browser and go to the Solution Package for Solace:

  8. http://IPAddress:8068/rtview-solmon if you are executing your browser on a different host than where the monitor is running.

    http://localhost:8068/rtview-solmon if you are executing your browser in the same host where the monitor is running.

    Use rtvadmin/rtvadmin for username/password.

    pubsubMonMain.gif

    You should now see monitoring data. If you encounter issues, check the log files in the SolacePubSubMonitor/projects/rtview-server/log directory for errors.

  9. If you are going to:

Obtain SEMP Version

This section only applies to Solace Cloud Event Brokers. You need to provide the exact SEMP version on each of your Solace Cloud Brokers.

Use the Solace Cloud console to get the value for the Solace Broker Version field, under Stats. The broker version aligns with the SEMP v1 version. You will use the first three digits, including any decimal points, of the value shown in the Solace Cloud Event Broker Solace Broker Version field, concatenated with this string: VMR.

For example, if the value for the Solace Broker Version field is 9.1.1.1.0, you enter: 9.1.1VMR