Obtain SEMP Version

Skip this step if your Solace software broker message brokers are using Solace PubSub+ version 8.7+ and Solace Appliance version 8.3+. This step is required if your Solace PubSub+ message brokers are using software versions prior to Solace PubSub+ version 8.7+ and Solace Appliance version 8.3+.

Note: It is recommended to not include a SEMP version string in commands, and only include one if a known deprecated behavior is needed from a particular SEMP schema.

In order to properly request monitored data, the Monitor requires the exact SEMP version on your message brokers. These instructions describe how to use SolAdmin to determine the SEMP version for each of your Solace message brokers or PubSub+ software. You will need this information when you connect your message brokers and edit connection properties.

Note: These instructions are for SolAdmin on Windows. For Linux, only the path to the log file changes.

1. Navigate to the SolAdmin installation folder. For example, C:\Program Files (x86)\SolAdmin\.

2. Change directory (cd) to the bin directory and open the log4j.properties file in a text editor.

3. Change the logging level to DEBUG and provide the full path to the logging file (for example, C:\Logs) while retaining all other settings. The edited properties are as follows:

# full path to the location where you want the log file to be stored. In this example C:\Logs

log4j.appender.A1.File=C:\Logs\soladmin.log
# Set the logging category to DEBUG
log4j.category.com.solacesystems=DEBUG, A1

4. Save the log4j.properties file.

5. Start SolAdmin and add your message brokers or PubSub+ software as managed instances.

6. Open the soladmin.log file and locate the semp-version tag in SEMP requests. The SEMP version that will be used by the Monitor replaces underscores (_) with dots (.). For example, if the SEMP request in the SolAdmin log file is 7_2VMR, you use 7.2VMR for the $solSempVersion substitution of the Monitor connection property.

Return to Quick Start .