We have the following use case: we are building a LCA with DOM which needs data from drivers to be converted and stored in DOM (so synchronized). The LCA will contain a mapping from "protocol / table / element" to a script. This script will then be responsible for converting data from the driver into a DOM instance.
What we are looking the best way for new/updated data on a driver (be it a new/updated element, dve, row in a table ...) to trigger these scripts. The solution should be a driver independent as possible, meaning we don't want to have to make changes to the driver each time a new mapping script is added to LCA.
Now we are trying out correlation rules which trigger on information events, but that might not be the most stable solution for the future. Maybe similar solutions already exist? Any input on this is much appreciated.
First of all, I believe what you are trying to achieve will be a bit complex to maintain. When copying data from an element to DOM, basically you will have two places (in the DataMiner deployment) where you will store the same information. Is it not an option to get data directly from the element?
That being said, if your workflow still requires to ingest data from an element to DOM, instead of taking an eventing approach (subscribe to table updates), is it not an option to use a polling approach? For example, I will execute my script every hour to get data from a table and update my DOM instances accordingly.
Hope it helps.