These instructions are for those customers who wish to evaluate the Solution Package for Solace for purchase. These are the minimum steps required to gather monitoring data and get the Monitor up and running. Default settings are used and Apache Tomcat, which is delivered with the Monitor, is preconfigured as the default application server.
After you complete your evaluation, if you wish to setup and use all monitoring features in your organization, see Configuration .
Obtain login credentials for each Solace broker you wish to monitor.
Java JDK 1.8 64 bit
Set the JAVA_HOME environment variable to point to your Java installation. For example:
UNIX
export JAVA_HOME=/opt/Java/jdk1.8.0
Windows
set JAVA_HOME=C:\Java\jdk1.8.0
Linux Users:
These instructions require a Bourne-compatible shell.
JAVA_HOME is required to be in the PATH for Tomcat to start correctly.
Download SolacePubSubMonitor_<version>.zip to your local server and extract the files: unzip -a SolacePubSubMonitor_<version>.zip
Important: On UNIX systems it is a requirement that the installation directory path not contain spaces.
Navigate to the SolacePubSubMonitor/bin directory and execute ./start_servers.sh -eval (start_servers.bat -eval in Windows).
NOTE: To stop the PubSub+ Monitor when it’s running in evaluation mode, execute ./start_servers.sh -eval (start_servers.bat -eval in Windows).
Browse to the following URL and login (rtvadmin/rtvadmin) to open the RTView Configuration Application HOME page:
http://IPAddress:8068/rtview-solmon-rtvadmin if you are executing your browser on a different host than where the monitor is running.
http://localhost:8068/rtview-solmon-rtvadmin if you are executing your browser in the same host where the monitor is running.
Select the Solace Monitor project to open the Solace configuration page.
Select Solace in the navigation tree (left panel), then click to add a broker connection.
Tip: Gray text shows the default setting for the field which you can edit. To return to the default setting, delete the text you entered.
In the Add Connection dialog do the following:
Toggle ON Edition if your broker is a PubSub+ Event Broker as a service instance.
For Cloud Service Brokers, enter the Connection Name, URL, Username, Password, SEMP Version* and VPN Name. Turn on the SSL Connection toggle if your broker is SSL Secured. See Obtain SEMP Version for instructions about getting the SEMP version installed in your message brokers.
For Non-Cloud Service Brokers, enter the Connection Name, Host:Port, Username and Password. If the broker is secured, the URL should use https instead of http.
If you are connecting via SSL, toggle ON SSL Secured, select SECURITY (in the navigation tree) and fill in the SSL Credentials section with the appropriate Truststore Location and Truststore Password values for your Brokers.
Repeat these steps to add more brokers and when finished, click to close the dialog and
(in title bar) to save your settings.
The connections you created are listed in the Connections tab.
Click to apply changes. The data server will be available again in 10-15 seconds.
Browse to the Solution Package for Solace and login (username/password are rtvadmin/rtvadmin):
http://IPAdress:8068/rtview-solmon if you are running the monitor remotely
http://localhost:8068/rtview-solmon if you are running the monitor locally
You should now see monitoring data. If you encounter issues, check the log files in the SolacePubSubMonitor/projects/rtview-server/log directory for errors.
You have completed the Quick Start!
To stop the PubSub+ Monitor, execute ./start_servers.sh -eval (start_servers.bat -eval in Windows).
If you wish to setup and use all monitoring features in your organization, proceed to Configuration .