Using SEMP

Solace Element Management Protocol version 2 (SEMP v2) is a RESTful API that you can use to configure Solace message routers. It complements the Solace router CLI and SolAdmin thick client GUI and provides a programmatic way to apply configurations to Solace message routers.

You use the following to learn about using SEMP:

  • Get Started—Tutorials are provided on the Solace Developer portal to walk you through how to execute a few SEMP commands natively in HTTP and through an auto-generated client library.
  • SEMP Concepts—This section provides an overview of the SEMP API and its key concepts.
  • API reference—Developer API documentation that covers SEMP's REST resources.
  • Legacy SEMP—This section provides information on how to use the legacy SEMP API which existed prior to SEMP v2.

SEMP v2 Limitations

The SEMP v2 API is being released iteratively with an initial focus on enabling Message VPN configuration on Solace routers. With each release, more commands and more functionality will be added. Below is a summary of the current support in SEMP v2. For commands and operations not yet supported in SEMP v2, you must use the legacy SEMP API.

Supported

  • Most Message VPN configuration commands (see exceptions below).

Unsupported

The following commands and operations are currently unsupported:

  • All admin commands
  • All monitoring commands
  • Most system level configuration commands.
  • For Message VPNs, configuration of the following features are not yet supported:
    • MQTT
    • topic replication
    • topic endpoint
    • JNDI