This article describes how to update the custom properties of an existing ActiveMQ network connector using the REST API.
Endpoint PATCH /activemq/network-connectors/{nodeName}/{managerName}/{brokerName}/{networkConnectorName}/custom-properties
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 retrieve.
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.
Request Body {
"test1": "success",
"test2": "success",
"test3": "done"
} Example Request curl -X 'PATCH' \
'http://172.16.31.68:8019/rest/v1/activemq/network-connectors/REMOTE_ACTIVEMQ/Activemq-16/DemoBroker/local-network/custom-properties' \
-H 'accept: */*' \
-H 'Authorization: Basic QWRtaW46YWRtaW4=' \
-H 'Content-Type: application/json' \
-d '{
"test1": "success",
"test2": "success",
"test3": "done"
}' Request URL http://localhost:8019/rest/v1/activemq/network-connectors/REMOTE_ACTIVEMQ/Activemq-16/DemoBroker/local-network/custom-properties Response Codes
Status Code
Description
204
Object changed
304
Object not changed
Example Response
Success Response (204-Object changed) : Indicates that the custom properties of the specified ActiveMQ network connector were successfully updated. No response body is returned. Reference Articles Using the REST API using the Navigator demo system
Performing REST API operations using the Swagger UI