Tango Archiving - TANGO Controls

# 9 years ago
girardot	Hello Balkrishna No, sorry, there is no shortcut, unless you write a script to do that… Regards, Raphaël Girardot Rg

# 9 years ago
TCS_GMRT	Hi Rapheal In View Configuration panel of Mambo, You can see the retrieved data. Also When you right click, you can save the data by clicking on save data file. Now I want to save that data automatically on My PC daily. How could I achieve it ? Where do I have to configure the settings ? Thanks and Regards TCS-GMRT Team Regards, TCS_GMRT

# 9 years ago
girardot	Hello The option to save data file is poposed by the Chart Mambo uses. This is not really a feature proposed by Mambo itself, and there is no way to do such things automatically using Mambo. However, you might use scripts to interact with HdbExtractor and TdbExtractor devices. Regards, Raphaël Girardot Rg

# 9 years ago
TCS_GMRT	Hi Rapheal Thanks for the suggestions to above questions. Also in TDB, I am not able to export the data to TDB. What is the reason? What DbPath, DsPath I have to set? Could you please explain by some example ?? Thanks and Regards TCS-GMRT Team Regards, TCS_GMRT

# 9 years ago
girardot	Hello Also in TDB, I am not able to export the data to TDB. What is the reason? What DbPath, DsPath I have to set? Could you please explain by some example ?? Each TdbArchiver has 2 mandatory properties DbPath DsPath DsPath is the path at which the archiver can write its file before eporting data to TDB DbPath is the path at which the DataBase can read the file. The reason of this is quite simple : HDB and TDB do not write data at the same frequency. Data writing is more frequent in TDB. As archiving project started, high rate data writing in database could not be done, due to too slow databases and/or connections. So, as a workaround, it was decided for TDB to buffer data in files (at DsPath folder) that should be read by the database later. With MySQL, we use the LOAD DATA LOCAL INFILE with DbPath. Generally, DbPath and DsPath will have the same value. So, of course, if your DbPath and DsPath do not match a valid directory, data won't be written in database. And if you ask me why 2 attributes instead of 1, I really don't remember, but as it was created this way and it worked like this since a long time now, we did not take neither time nore risk to change it. I hope these explanations will help you with your data export problem. Regards, Raphaël Girardot Rg Edited 9 years ago

# 9 years ago

girardot

Hello

Also in TDB, I am not able to export the data to TDB. What is the reason? What DbPath, DsPath I have to set?
Could you please explain by some example ??

Each TdbArchiver has 2 mandatory properties
DbPath
DsPath

DsPath is the path at which the archiver can write its file before eporting data to TDB
DbPath is the path at which the DataBase can read the file.

The reason of this is quite simple : HDB and TDB do not write data at the same frequency. Data writing is more frequent in TDB. As archiving project started, high rate data writing in database could not be done, due to too slow databases and/or connections. So, as a workaround, it was decided for TDB to buffer data in files (at DsPath folder) that should be read by the database later.

With MySQL, we use the LOAD DATA LOCAL INFILE with DbPath.

Generally, DbPath and DsPath will have the same value.

So, of course, if your DbPath and DsPath do not match a valid directory, data won't be written in database.

And if you ask me why 2 attributes instead of 1, I really don't remember, but as it was created this way and it worked like this since a long time now, we did not take neither time nore risk to change it.

I hope these explanations will help you with your data export problem.

Regards,

Raphaël Girardot

Edited 9 years ago

# 9 years ago
Po	Hello Team, Thank you for all the above answers and it helped a lot. I'm currently exploring data archiving with Tango and able to archive the data successfully with HDB (MySQL). I learned that HDB supports Oracle/MySQL and HDB++ supports Cassandra at back-end. Here are the stuffs on which I need help: 1. Link to download HDB++ & its GUI(Not present in downloads tab of the Tango site). If HDB++ is not released yet, may I get any Beta copy to explore further? Also checked on sourceforge.net but could not interpret further. 2. Any documentation/guidance on how to use HDB++ other than the EventSubscriber & ConfigurationManager class details; like HDB? 3. Just for curiosity, is it possible to have Cassandra compability with HDB? Eagerly waiting for the reply. Kind regards, Jyotin Ranpura ——————— "Nothing comes to you, it comes for you!" - Joel Osteen

# 9 years ago

Hello Team,

Thank you for all the above answers and it helped a lot.

I'm currently exploring data archiving with Tango and able to archive the data successfully with HDB (MySQL). I learned that HDB supports Oracle/MySQL and HDB++ supports Cassandra at back-end.

Here are the stuffs on which I need help:

Eagerly waiting for the reply.

Kind regards,
Jyotin Ranpura
———————

"Nothing comes to you, it comes for you!" - Joel Osteen

# 9 years ago
girardot	Hello. Concerning your 3rd question, there is a discussion about reunifying the archiving systems, so that mambo may extract your data whatever the archiving system you used. And it implies having HDB compatible with cassendra. But none of this is done yet. There is a great work to do to reach this goal, which is still in discussion anyway. So no, it is not yet possible to have Cassendra compatible with HDB, but it is in the TODO list… Rg

# 9 years ago

girardot

Hello. Concerning your 3rd question, there is a discussion about reunifying the archiving systems, so that mambo may extract your data whatever the archiving system you used. And it implies having HDB compatible with cassendra. But none of this is done yet. There is a great work to do to reach this goal, which is still in discussion anyway. So no, it is not yet possible to have Cassendra compatible with HDB, but it is in the TODO list…

# 9 years ago
Po	girardot Hello. Concerning your 3rd question, there is a discussion about reunifying the archiving systems, so that mambo may extract your data whatever the archiving system you used. And it implies having HDB compatible with cassendra. But none of this is done yet. There is a great work to do to reach this goal, which is still in discussion anyway. So no, it is not yet possible to have Cassendra compatible with HDB, but it is in the TODO list… Thanks Girardot, got your point.

# 9 years ago

girardot
Hello. Concerning your 3rd question, there is a discussion about reunifying the archiving systems, so that mambo may extract your data whatever the archiving system you used. And it implies having HDB compatible with cassendra. But none of this is done yet. There is a great work to do to reach this goal, which is still in discussion anyway. So no, it is not yet possible to have Cassendra compatible with HDB, but it is in the TODO list…

Thanks Girardot, got your point.

# 9 years ago
lorenzo	Hi Jyotin, just for completness, hdb++ supports both MySQL and Cassandra as back-ends. You can get hdb++ from sourceforge: http://sourceforge.net/p/tango-cs/code/HEAD/tree/archiving/hdb++/ where you can find also some documentation, as the original design guidelines. Using hdb++ is, indeed, quite simple: 1) create the database on the back-end engine 2) create at least one EventSubscriber device server 3) create one ConfigurationManager device server 4) use Jive or the ConfigurationManager GUI to setup the events for attributes of the TANGO devices you want to archive Of course some additional documentation is forseen. Cheers, Lorenzo

# 9 years ago

lorenzo

Hi Jyotin,
just for completness, hdb++ supports both MySQL and Cassandra as back-ends.
You can get hdb++ from sourceforge:
http://sourceforge.net/p/tango-cs/code/HEAD/tree/archiving/hdb++/
where you can find also some documentation, as the original design guidelines.
Using hdb++ is, indeed, quite simple:
1) create the database on the back-end engine
2) create at least one EventSubscriber device server
3) create one ConfigurationManager device server
4) use Jive or the ConfigurationManager GUI to setup
the events for attributes of the TANGO devices you want to archive
Of course some additional documentation is forseen.

Cheers,
Lorenzo

# 9 years ago
Po	lorenzo Hi Jyotin, just for completness, hdb++ supports both MySQL and Cassandra as back-ends. You can get hdb++ from sourceforge: http://sourceforge.net/p/tango-cs/code/HEAD/tree/archiving/hdb++/ where you can find also some documentation, as the original design guidelines. Using hdb++ is, indeed, quite simple: 1) create the database on the back-end engine 2) create at least one EventSubscriber device server 3) create one ConfigurationManager device server 4) use Jive or the ConfigurationManager GUI to setup the events for attributes of the TANGO devices you want to archive Of course some additional documentation is forseen. Cheers, Lorenzo Thank you very much Lorenzo. Cheers!

# 9 years ago

lorenzo
Hi Jyotin,
just for completness, hdb++ supports both MySQL and Cassandra as back-ends.
You can get hdb++ from sourceforge:
http://sourceforge.net/p/tango-cs/code/HEAD/tree/archiving/hdb++/
where you can find also some documentation, as the original design guidelines.
Using hdb++ is, indeed, quite simple:
1) create the database on the back-end engine
2) create at least one EventSubscriber device server
3) create one ConfigurationManager device server
4) use Jive or the ConfigurationManager GUI to setup
the events for attributes of the TANGO devices you want to archive
Of course some additional documentation is forseen.

Cheers,
Lorenzo

Thank you very much Lorenzo. Cheers!