Good afternoon!
For days we are having problems for the configuration of cygnus in relation
to MySQL, since and as Fermín Galan recommended us, we want to save the
historical data in an external database, in this way we will always have
access to the historical data in a more comfortable and fast method.
I explain step by step and with images our process carried out.

1º We have deployed an instance of Orion in our Fiware Lab. Then we have
configured our security group, as we have obtained the key pair and at our
O.ContextBroker we have associated a public ip.

2º Then using puttygen we have generated our ppk, then we have made the SSH
connection through Putty and using the user "centos".

3º In this step we have used the guide https://github.com/
telefonicaid/fiware-cygnus/blob/master/doc/cygnus-ngsi/quick_start_guide.md.
We have executed the following instruction

*$ sudo cat> /etc/yum.repos.d/fiware.repo << EOL[Fiware]name = FIWARE
repositorybaseurl = http: //repositories.lab.fiware.org/repo/rpm/6/
<http://repositories.lab.fiware.org/repo/rpm/6/>gpgcheck = 0enabled = 1EOL**$
sudo yum install cygnus*

And we have updated the cygnus instacia that was included with our OrionCT.
(image1.png)

4th Then we have installed Java SDK, which has been installed correctly
(image2.png).

5º Next we have generated the variable JAVA_HOME permanently, editing / etc
/ profile (image3.png)

sudo vi / etc / profile

6º We have gone on to create our file cygnus_instance_1.conf and our file
agent_1.conf. (Image4.conf)

7º Using *sudo vi /usr/cygnus/conf/cygnus_instance_1.conf *and *sudo vi
/usr/cygnus/conf/agent_1.conf*, we have created our configuration files
(agent_1.txt and cygnus_instance_1.txt).

8º Then we have created our subscription, so that when the start time of
the activity stored in Orion is modified, it sends a notification to
Cygnus. (image5.png).

9º Making use of OrionExplorer I have verified that the subscription has
been created correctly (image6.png).

10º We do a quick test of operation to see that if we updating our entity,
the history can is generated in MySQL. We have seen that the subscription
works (image7.png), but the table with the historical ones is not generated
in our server.

In what section are we doing something wrong? This is the only step we need
to store the data automatically, this way we can generate the .geojson
files with a single step and thanks to the fiware technology, but
unfortunately we have not yet been able to fix this problem.

I have attached the cygnus.log that I obtained when running Cygnus as a
service "sudo service cygnus start 1"

Thank you very much for your help!
Best regards!

–

Francisco José Melgar Molina
CTO Ciclogreen

francisco.melgar@ciclogreen.com · www.ciclogreen.com

41092 · Sevilla

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

__________________________________________________________________________________________

You can get more information about our cookies and privacy policies on the following links:

• http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy
• http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE

Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help

[Created via e-mail received from: Fran Melgar <francisco.melgar@ciclogreen.com>]