Delete an adapter component

When you remove an adapter 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.

Note: OmfEgress component is required and cannot be deleted.

To delete an adapter component:

1. Start any of the Configuration tools capable of making HTTP (Hypertext Transfer Protocol) requests.

2. Run a DELETE command to the following endpoint:

   Definition: The DELETE method is used to remove data from a database.

   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.

File relocation

All configuration and log files are renamed and moved. 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 location:

Windows: %programdata%\Structured Data Files\Adapters\Structured Data Files\Configuration\Removed

Linux: /usr/share\Structured Data Files/Adapters/Structured Data Files/Configuration/Removed

Log files are moved to the following location:

Windows: %programdata%\Structured Data Files\Adapters\Structured Data Files\Logs\Removed

Linux: /usr/share\Structured Data Files/Adapters/Structured Data Files/Logs/Removed

In the following example, one adapter service is installed on a particular Windows node with the name <Adapter>Service1. An adapter component with the name <Adapter>DeviceX was added and configured to this adapter and later removed. Linux follows a similar behavior. This is the resulting relocation and renaming scheme after deletion: