Disassociating Agents from Managers in a Redundant Setup

Use this API to unassign agents from the eG managers in a redundant setup.

URL: http://<eG manager IP:port>/api/eg/orchestration/unassignagents

Method: POST

Content-Type: application/json

Inputs to be Specified

Parameters	Key values	Example
Headers	managerurl: Base URL of the eG Manager i.e., http://<IP address of the eG console:Port> user: eG username or domain/eG username pwd: Base64 encoded password	{ "managerip:"192.168.8.104", "agents":"gen1,ora8" }
Body	Default: { "managerip":"IP of the eG manager from which agents are to be delinked", "agents":"Comma-separated list of agents" }

 

Success Response

Type	Code	Content
JSON	200	{ "Succeed": "one or more agents unassigned successfully." }

Figure 1 : Unassign agents from the eG managers in a redundant setup using Postman REST Client

Disassociating Agents from Managers in a Redundant Setup using cURL

To unassign agents from the eG managers in a redundant setup through the REST API using cURL, the command should be specified in the following format:

curl --location --request POST "http://<eG Manager IP:Port>/api/eg/orchestration/unassignagents" -H "managerurl:http://<eG Manager IP:Port>" -H "user:<eG username or domain/eG username>" -H "pwd:Base64 encoded password" -H "Content-Type: application/json" --data-raw "{'managerip':'IP of the eG manager from which agents are to be delinked', 'agents':'Comma-separated list of agents'}"

Figure 2 shows an example of unassigning agents from the eG managers in a redundant setup using cURL.

Figure 2 : Unassigning agents from the eG managers in a redundant setup using cURL