SEMP API Reference

There are two SEMP API Reference guides available depending on whether using PubSub+ software event brokers or PubSub+ appliances. You can access the SEMP API Reference in two ways:

Connect to the PubSub+software event broker or appliance using a web browser:

Enter the following URL in a web browser that has connectivity to your host event broker (either a PubSub+software event broker or appliance). For example:

http://<HOST>/SEMP/v2/config/help

Where: <HOST> is the IP address of your event broker. If the host is a Solace PubSub+ software event broker, append :8080 to the IP address.

If you want to access the SEMP Swagger specification file (for example, to Generate a SEMP Client Library), enter the following URL:

http://<HOST>/SEMP/v2/config/spec

Click the appropriate link below to see the Configuration, Action, or Monitoring reference for software event brokers and appliances:

Migrating swagger-codegen Java client code from before v9.6 to v9.6 or later

In version 9.6, SEMP version 2.17 added a new query parameter called opaquePassword. When a new client library is generated for this version using swagger-codegen, the method signatures for API calls may have changed in a backwards-incompatible way for some languages.

In Java libraries generated from SEMP version 2.17, all API calls have a new parameter for opaquePassword. Existing code using the new generated library does not compile until a value is provided for this new parameter. You must provide a value of null for each instance of this parameter to preserve the behavior of the existing code.

Alternatively, to avoid these changes to method signatures altogether, you can manually delete the section of the Swagger specification describing the opaquePassword query parameter. However, until your code is updated, you must perform this editing every time you upgrade and regenerate the client library.