On my DataMiner system are a lot of GQI custom operators present. The problem with this is that selecting an operator to use is hard when there are so many (plenty are unused).
Another thing I noticed is that sometimes when updating the custom operator script, the same operator is present twice in the available operator's list (the old version and the new one).
Is there a way to see all available operators and clean up/delete some?
Same for data source.
Hi Dieter,
I assume there are better/cleaner ways when on a production cluster. But if it's just on your local DataMiner testing out operators or ad hoc data sources, I think an easy way is to remove the *.dll's out of the folder C:\Skyline DataMiner\Scripts\Libraries. That's at least how I do it when I am testing. 😊
Kind regards,
Joachim
Hi. I think the ones that are still on your DMA, the DLL will get recreated when you click on “Save as a Script” in the Automation Module with the checkbox “Compile as library with name” checked.
You can also check the names of the DLLs, and only remove the ones that you want to get rid of. The name is like this:
“[Automation Script Name].[What You typed in Compile as Library with Name Textbox].[DateTime when compiled].dll”.
Note that in for example the Dasboards-app, if you there select “Get ad hoc data”, the name of your ad hoc data source will be the “GQIMetaData-tag” you gave it.
I cannot see the code behind it, but what I think is that when fetching the list of possible ad hoc data sources, it goes to the abovementioned folders, and checks all available GQIMetaData-tags. If there are two with the same GQIMetaData-tag, but with another dllname, you see this behind brackets ‘()’.
Also, for your concern to accidently remove things, the “source code” is still in the C:Skyline DataminerScripts- folder. So by removing DLLs in the ScriptsLibraries-folder you will not loose source code.
If other people read this answer, note that this explanation is just for a personal DataMiner. I am not sure what is the behaviour on a cluster (concerning how this changes could get synced), so this answer is only applicable for testing environment.
Thanks for the answer, but I have 1 additional question.
If I remove the *.dll will this also remove the script on my DMA?
Or will the *.dll get added again for scripts that still exist?
(I don’t want to accidentally remove useful things)