suppliers:hvac.io:vigilia:installation
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
suppliers:hvac.io:vigilia:installation [2020/07/22 15:01] – old revision restored (2015/07/30 01:52) 95.91.41.38 | suppliers:hvac.io:vigilia:installation [2020/07/22 15:02] – old revision restored (2015/09/14 13:19) 95.91.41.38 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Installation ====== | + | ====== |
- | For self-hosted version only. To use the HVAC.IO servers instead, [[https:// | + | //**For self-hosted version only.** To use the HVAC.IO servers instead, [[https:// |
The installation is separated in 3 main components: | The installation is separated in 3 main components: | ||
Line 11: | Line 11: | ||
They can all be installed on the same machine, or on separate servers and devices, depending on your network architecture. | They can all be installed on the same machine, or on separate servers and devices, depending on your network architecture. | ||
+ | |||
+ | Once this is done, you might want to take a look at [[#Adding Vigilia as a Service]] | ||
===== Database ===== | ===== Database ===== | ||
- | For the time being, Vigilia only supports [[http://www.tokutek.com/tokumx-for-mongodb/|TokuMX]]. | + | For the time being, Vigilia only supports [[https://www.percona.com/software/ |
It is a fork of MongoDB, which features mind boggling increase in performance and reduction in the database size. | It is a fork of MongoDB, which features mind boggling increase in performance and reduction in the database size. | ||
(The choice was not made lightly; we tried many databases before settling with this one.) | (The choice was not made lightly; we tried many databases before settling with this one.) | ||
Line 23: | Line 25: | ||
- | Download and install by following the instructions on this [[http://www.tokutek.com/ | + | Download and install by following the instructions on this [[https://www.percona.com/downloads/ |
===== Vigilia Server ===== | ===== Vigilia Server ===== | ||
Line 29: | Line 31: | ||
For maximum speed, we recommend you install the Vigilia server on the same machine as the database. | For maximum speed, we recommend you install the Vigilia server on the same machine as the database. | ||
- | Vigilia server runs on [[www.java.com|Java]], | + | Vigilia server runs on [[http://www.java.com|Java]], |
Line 53: | Line 55: | ||
< | < | ||
- | (where <port number> is the port you want to use.) | + | (where <port number> is the port you want to use. If you don't know which one to take, use 47900.) |
- | Obviously, if you want the application to start automatically when your server | + | After a few seconds, the server |
+ | You can now take your browser and go to: | ||
+ | < | ||
+ | |||
+ | If you want the application to start automatically when your server boot up, you should make sure to [[#Adding Vigilia as a Service|create a service]], or configure your web server (like Tomcat) to use vigilia-server.jar. | ||
===== Loggers ===== | ===== Loggers ===== | ||
+ | |||
+ | Loggers are software able to scan a BACnet network and send the data back to a Vigilia server. | ||
+ | |||
+ | The only publicly available logger is Wacnet (min version 1.8). | ||
+ | |||
+ | To start logging a network, you need to configure a few things in the **Vigilia Configs** page : | ||
+ | |||
+ | |||
+ | ==== Step 1: Connect to a Vigilia server ==== | ||
+ | |||
+ | //**For self-hosting only.** Users of HVAC.IO' | ||
+ | |||
+ | The first thing to configure is a Vigilia API URL. This will tell Wacnet where it should send its data. | ||
+ | |||
+ | It should have the following form: | ||
+ | |||
+ | < | ||
+ | http://< | ||
+ | </ | ||
+ | |||
+ | |||
+ | Make sure Wacnet can see the provided URL! | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | ==== Step 2: Project credentials ==== | ||
+ | |||
+ | You have to provide a **project ID** and a **logging key/ | ||
+ | Both are available through the project configurations on the Vigilia server. | ||
+ | |||
+ | Here's an example : | ||
+ | * Project-id : 5371147be4b0222b740851a2 | ||
+ | * Logging key: asdi34h5ha | ||
+ | |||
+ | Make sure Wacnet has access to the project : | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | ==== Start Logging ==== | ||
+ | |||
+ | When Wacnet starts, it searches for Vigilia configurations. If it finds some, **it will start logging automatically**. | ||
+ | |||
+ | To start the logging without restarting Wacnet, expand the details part of the page and click on " | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Adding Vigilia as a Service ===== | ||
+ | |||
+ | You might want to make sure the Vigilia server always starts as soon as the server boots, or that it restores itself in case of a crash. | ||
+ | |||
+ | For this, you'll have to add Vigilia as a service. | ||
+ | |||
+ | Start by creating a file named " | ||
+ | |||
+ | Open it and paste the following: | ||
+ | |||
+ | |||
+ | <code shell> | ||
+ | |||
+ | description " | ||
+ | author " | ||
+ | |||
+ | start on runlevel [2345] | ||
+ | stop on runlevel [!2345] | ||
+ | |||
+ | |||
+ | #Respawn the process if it crashes | ||
+ | #If it respawns more than 10 times in 60 seconds stop | ||
+ | respawn | ||
+ | respawn limit 10 60 | ||
+ | |||
+ | expect fork | ||
+ | |||
+ | #replace PATH-TO-THE-JAR with something like / | ||
+ | #replace PORT with the desired port number | ||
+ | script | ||
+ | cd PATH-TO-THE-JAR | ||
+ | java -jar vigilia-server.jar PORT & | ||
+ | end script | ||
+ | |||
+ | </ | ||
+ | |||
+ | Now, once you replaced PATH-TO-THE-JAR and PORT with their correct values, move the file to /etc/init: | ||
+ | |||
+ | < | ||
+ | sudo mv vigilia.conf / | ||
+ | </ | ||
+ | |||
+ | That's it! | ||
+ | Now reboot and Vigilia should start automatically. | ||
+ | |||
+ | To get more info about Upstart and services, see http:// | ||
+ |
suppliers/hvac.io/vigilia/installation.txt · Last modified: 2020/10/04 01:53 by 173.249.2.13