Generic Delete is an internal workflow, primarily used for testing purposes to delete test data. It is not intended or recommended for production regions. Purge and Archive Tool should be used for maintenance and data cleanup for clients environments.
A sample delete data IWS workflow solution, eagle_wrf_generic_delete, has been created. This solution extracts ZIP-packed data from the archives of the sample eagle_wrf_generic_extract solution and routes it to the eagle_ml-2-0_default_in_xml_delete_objects message stream. For this message stream, the inbound rule deletes records from the database based on the specific object type.
Please note, that eagle_ml-2-0_default_in_xml_delete_objects stream can delete only one record at a time
With this sample solution, you can:
- Start the delete data IWS workflow solution (Step 1).
Data deletion is triggered. - Unzip archived data (Step 2).
- Delete data from the database (Step 3).
The following diagram shows the overall structure of the sample delete data IWS workflow solution.
Start the Delete Data IWS Workflow Solution (Step 1)
You can start the eagle_wrf_generic_delete solution in several ways:
- Put a ZIP file directly into the data\msgcenter\msgcenter\in\RAW\eagle_ml-2-0_default_cm_ndfa\incoming folder.
The file name must match the EAGLEML_DELETE mask. - Send a Control Message specifying the ZIP file name and the archive location to the eagle_ml-2-0_default_cm_control_message stream.
- Send a Control Message with Base64 encoded data to the eagle_ml-2-0_default_cm_control_message stream.
Unzip Archived Data Extracts (Step 2)
This step is performed by the eagle_ml-2-0_default_cm_ndfa and eagle_ml-2-0_default_cm_unpacker message streams.
Delete Data from the Database (Step 3)
After the data is unzipped, a sequence of delete processes is run for different object groups. Each delete process starts when all the files for previous processes (defined by the filename mask) are deleted.
0 Comments