Quick Start

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.

Prerequisite(s):

 

  • Obtain login credentials for each Solace broker you wish to monitor.
  • A supported Java JDK (see System Requirements)
  • Set the JAVA_HOME environment variable to point to your Java installation, and add JAVA_HOME/bin to the PATH. For example:

    UNIX

    export JAVA_HOME=/opt/Java/jdk1.8.0
    export PATH=$PATH:$JAVA_HOME/bin

    Windows

    set JAVA_HOME=C:\Java\jdk1.8.0
    set PATH=%PATH%;%JAVA_HOME%\bin

  • Linux Users: These instructions require a Bourne-compatible shell.

 

To evaluate Solace PubSub+ Monitor:

  1. Install Solace PubSub+ Monitor

  2. Navigate to the SolacePubSubMonitor/bin directory and execute

    LINUX/UNIX: ./start_servers.sh -eval
    WINDOWS: start_servers.bat -eval

  3. 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.

  4. Select the Solace Monitor project to open the Solace configuration page.

    cui_solace_selectProject.gif

  5. Select Solace in the navigation tree (left panel), then click ConfigUI_Connections_Add_button.gif to add a broker connection.

    cui_solace_connects.gif

    6. 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.

  6. 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.

  7. 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.

    8. The connections you created are listed in the Connections tab.

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

  9. Browse to the Solace PubSub+ Monitor and login (username/password are rtvadmin/rtvadmin):

    10. http://IPAdress:8068/rtview-solmon if you are running the monitor remotely

    http://localhost:8068/rtview-solmon if you are running the monitor locally

    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.

    You have completed the Quick Start!

  10. To stop the Solace PubSub+ Monitor, execute
    LINUX/UNIX: /stop_servers.sh -eval
    WINDOWS: stop_servers.bat -eval

If you wish to setup and use all monitoring features in your organization, proceed to Configuration.