This article describes how to search for existing ActiveMQ network connector using the REST API.
Endpoint
GET/activemq/network-connectors
Query Parameters
| Parameter | Type | Required | Description |
nodeName |
string | No | Name of the ActiveMQ node. |
managerName |
string | No | Name of the ActiveMQ manager that contains the specified broker. |
brokerName |
string | No | Name of the ActiveMQ broker that contains the specified network connector. |
networkConnectorName |
string | No | Name of the ActiveMQ network connector to retrieve. |
projects |
string | No | A comma-separated list of project IDs |
filter |
string | No | Filters the results based on attribute values |
order |
string | No | Specifies the attributes by which to order the results |
limit |
integer | No | Limits the number of objects returned |
attributes |
string | No | A comma-separated list of attributes or attribute sections to retrieve |
validateAccessForUser |
string | No | Validates endpoint access for the specified user. |
Example Request
curl -X 'GET' \ 'http://localhost:8019/rest/v1/activemq/network-connectors' \ -H 'accept: application/json' \ -H 'Authorization: Basic <base64-encoded-credentials>'
Request URL
http://localhost:8019/rest/v1/activemq/network-connectors
Response Codes
| Status Code | Description |
| 200 | Returns matching objects |
Example Response
-
Success Response (200-Returns matching objects):
[ { "wgsName": "MQM", "nodeName": "REMOTE_ACTIVEMQ", "managerName": "Activemq-16", "brokerName": "DemoBroker", "networkConnectorName": "local-network" } ]Response headers:
content-type: application/json date: server: transfer-encoding: vary: