Data Source Scripted Connector

Solved612 viewspython Scripted Connectors
3
0 Comments

I created a connector using data source and python code. It's working fine and pulling data but when I'm exporting protocol, it doesn't have Qaction or protocol script, It only has params. Please help me how can i export with script or how can i export scripted connector & deploy on another DMA.

Thanks

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 27th August 2024

1 Answer

2
12.94K 3 Comments

Hi Vikas,

With Data Sources and Scripted Connectors there is no QAction or logic in the connector itselft so what you are experiencing is expected.

With Data Sources all the logic is outside the elements and in the python code and for now there is no way of automatically export everything as a package.

If you want to move your scripted connector to another system your options are to:

  • create it on the other system by placing your python code there and Data API will create a new element and push data.
  • if you want to keep the trending history, you can export the scripted connector element as if it were any other element and then configure the python script in the new system as well.
    Data API should find the element by its identifier and start pushing data to it.
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 27th August 2024
Vikas Choudhary [DevOps Member] commented

Thank you Joao Severino. I have another question now, if we have DMA cluster, do i need to do same process for all DMA or only i can upload on one and rest will be sync automatically?

If I need to do it manually on all cluster DMA’s,
1) will it be same element id on all agent ?
2) will script run on all DMA every minute?
3) Script calling third party api, will DMA DB have duplicate data in this case?

Thank you
João Severino [SLC] [DevOps Catalyst] commented

Hi, to answer your questions
1) If you have a cluster you only need to configure your data source in 1 of your agents. You can configure in multiple agents with different identifiers and in that case it will result in different elements.
If you configure the same identifier then DataMiner will notice that and set the parameter values always on the original element.
The exporting and importing only makes sense if you want to migrate your element not have duplicates.
2) Only in the agent where you configure your data source.
3) Not sure I understand this last question but data will be stored in DataMiner’s DB as any other ‘regular’ element.