Delete an AVEVA Events to CONNECT component
- Last UpdatedJul 31, 2024
- 2 minute read
When you remove an agent component, the configuration and log files are saved into a sub-directory in case they are needed later. Any associated types, streams, and data remain on the respective endpoints.
Complete the following steps to delete a component:
-
Start any of the configuration tools capable of making HTTP requests.
-
Run a DELETE command to the following endpoint: http://localhost:5590/api/v1/configuration/system/components/<ComponentId>
Note: You must make an empty DELETE command against the Id of the component you want to delete. 5590 is the default port number. If you selected a different port number, replace it with that value.
To delete a component:
Using Curl commands
To delete a component:
curl.exe --ntlm --negotiate -u <UserName> -X DELETE "http://localhost:5590/api/v1/configuration/system/components/<ComponentId>"
Using Configurator plugin

To delete a component:
-
Select an item of type EventsToCONNECT in the System Component list.
-
Select Delete.
File relocation
All configuration and log files are renamed and moved when a system component is deleted. The files are renamed according to the timestamp of removal, for example, FileName.json_removed_yyyy-MM-dd--hh-mm-ss.
Configuration files are moved to the following locations:
-
Windows: %ProgramData%\OSIsoft\Adapters\EventsToCONNECT\Configuration\Removed
-
Windows: %ProgramData%\OSIsoft\Adapters\EventsToCONNECT\Logs\Removed
In the following example, one service is installed on a particular Windows node with the name <Adapter>System. A component with the name <Adapter>DeviceX was added and configured and later removed. This is the resulting relocation and renaming scheme after deletion:




REST URLs
|
Relative URL |
HTTP verb |
Action |
|---|---|---|
|
api/v1/configuration/system/ components/<ComponentId> |
DELETE |
Deletes specified component |
Note: Replace ComponentId with the Id of the component that you want to delete.