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.

The SEMP API allows you to handle messaging as a service and makes it easy for you to provision, operate, and maintain Solace messaging wherever your applications need it, whether that is in the public cloud, your private cloud, or simply in your datacenter.

SEMP makes tasks like configuring objects and retrieving status data or statistics easy and efficient, even when supporting different versions of SolOS, and enables atomic “all or none” updates and creations. Client libraries can be generated in many languages, and rich online documentation makes it easy to use.

Using SEMP

SEMP is designed to integrate easily into your DevOps workflow and with popular CI tools so you can easily roll out messaging along with applications. It can be easily integrated into configuration management portals or with configuration automation tools like Chef, Puppet and Ansible so you have to write very little code.

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 is a new REST API which is being introduced incrementally. To understand current limitations, click here.