This article describes how to start an existing ActiveMQ network connector using the REST API.
Endpoint
POST/activemq/network-connectors/{nodeName}/{managerName}/{brokerName}/{networkConnectorName}/start
Path Parameters
| Parameter | Type | Required | Description |
nodeName |
string | Yes | Name of the ActiveMQ node. |
managerName |
string | Yes | Name of the ActiveMQ manager that contains the specified broker. |
brokerName |
string | Yes | Name of the ActiveMQ broker that contains the specified network connector. |
networkConnectorName |
string | Yes | Name of the ActiveMQ network connector to start. |
Query Parameters
| Parameter | Type | Required | Description |
jobDate |
integer | No | Schedule job date (Unix Timestamp). |
jobTags |
string | No | A comma-separated list of schedule job tags (used only with jobDate). |
validateAccessForUser |
string | No | Validates endpoint access for the specified user. |
Example Request
curl -X 'POST' \ 'http://localhost:8019/rest/v1/activemq/network-connectors/REMOTE_ACTIVEMQ/Activemq-16/DemoBroker/local-network/start' \ -H 'accept: */*' \ -H 'Authorization: Basic <base64-encoded-credentials> \ -d '
Request URL
http://localhost:8019/rest/v1/activemq/network-connectors/REMOTE_ACTIVEMQ/Activemq-16/DemoBroker/local-network/start
Response Codes
| Status Code | Description |
| 201 | Object created |
| 304 | Action Failed |
Example Response
-
Success Response (201- Object created): Indicates that the ActiveMQ network connector was successfully started. No response body is returned.
Response headers:
access-control-allow-credentials: true access-control-allow-origin: http://localhost:8019 content-length: 0 date: server: vary:
-
Example Error Response: 404-Error: Bad Request
{ "type": "pcf", "messageId": "WGS0038", "message": "Command not executed", "explanation": "Problem on executing command, check PCF response code value.", "action": "Resubmit request with a valid object.", "code": "2059", "codeStr": "MQRC_Q_MGR_NOT_AVAILABLE" }