The protocols and port numbers of the connection endpoint. The serviceManagementTlsListenPort and serviceSmfTlsListenPort protocols along with the port numbers must be specified in the request.

Connection specific protocols.

Solace Messaging

'serviceSmfPlainTextListenPort'-Use SMF Host (plain-text) over TCP to connect and exchange messages with the event broker service.
'serviceSmfCompressedListenPort'-Use SMF (plain-text) in a compressed format over TCP to connect and exchange messages with the event broker service.
'serviceSmfTlsListenPort'-Use secure SMF using TLS over TCP.

Solace Web Messaging

'serviceWebPlainTextListenPort'-Use WebSocket over HTTP (plain-text).
'serviceWebTlsListenPort'-Use WebSocket over secured HTTP.

AMQP

'serviceAmqpPlainTextListenPort'-Use AMQP (plain-text).
'serviceAmqpTlsListenPort'-Use AMQP over a secure TCP connection.

MQTT

'serviceMqttPlainTextListenPort'-Use MQTT (plain-text).
'serviceMqttWebSocketListenPort'-Use MQTT WebSocket (plain-text).
'serviceMqttTlsListenPort'-Use secure MQTT.
'serviceMqttTlsWebSocketListenPort'-Use WebSocket secured MQTT.

REST

'serviceRestIncomingPlainTextListenPort'-Use REST messaging (plain-text).
'serviceRestIncomingTlsListenPort'-Use secure REST messaging.

Management

'serviceManagementTlsListenPort'-Use the secured management connection, which uses SEMP to manage the event broker. This port must be enabled on at least one of the service connection endpoints on the event broker service.
'managementSshTlsListenPort'-Use a secure port to connect to the event broker service to issue Solace Command Line Interface (CLI). This port provides you with scope-restricted access to the event broker service.

Optional for updates - only provided ports will be modified.

201Created.

400Bad request.

401Unauthorized.

403Forbidden.

404Entity Not Found.