Which means that the client has communicated. sudo a2enmod ssl proxy_http proxy_wstunnel rewriteįor unencrypted traffic, the standard default configuration "/etc/apache2/sites-available/nf" entry is:ĬustomLog $. sudo systemctl edit -full rviceįor client traffic, support for the tunnelling of web socket connections from a Traccar client to a self-hosted backend Traccar server websocket at say is needed. For example, set "WatchdogSec = 600" using: It was felt at some stage that it might be wise to increase the systemd restart time delay by editing the traccar service configuration. sudo /opt/traccar/jre/bin/java -jar tracker-server.jar conf/traccar.xmlĪnd it is perhaps useful to note that Traccar is installed with its own Java so there is no need to worry about one's globally installed Java versions.It is sometimes useful to start traccar manually, especially if there is an error in the traccar.xml configuration file: Traffic between a client and the Traccar server can be monitored using the Traccar log file at "/opt/traccar/log/traccar-server.log". The Traccar web interface runs on port 8082 ( and the Traccar installation creates a default user (login = "admin" password = "admin") and the IMEI number of a mobile device is used as the unique identifier (for an Android phone, the IMEI number is found under "Settings -> About phone"). The integrated Traccar-OpenGTS setup also works with a reverse proxy for port 5055, i.e., for the Traccar Client one can use an https address of the form: This is also the case for Traccar integrated with OpenGTS where Traccar writes data to an OpenGTS database called say "gts".īoth the Traccar and OpenGTS web interfaces will of course require encrypted traffic so the fact that the Traccar Client (and indeed the mGTS Client for OpenGTS) do not require encrypted traffic does not mean that one can ignore setting up a reverse proxy for encrypted traffic. With an Apache2 webserver set up as a reverse proxy for both normal and unencrypted data traffic, the server URL in the Traccar Client can be of the form: The Traccar server "default.xml" file shows that osmand uses port 5055. Recent versions of the Traccar Client use the OsmAnd protocol to report GPS data. An OpenGTS database however needs to be MyISAM. The Traccar installation ensures that InnoDB is used. It is perhaps useful to know that the Tracar database uses the InnoDB storage engine. Updating of the database structure should also be disabled by removing the entry: Jdbc:mysql://127.0.0:3306/traccar?allowMultiQueries=true?įor default.xml, it is probably wise to disable the geocoder:Īnd to remove the other geocoder entries. The traccar installation creates a database called "traccar" with "root" as the user so traccar.xml needs to be edited in the obvious way: The important entries in "traccar.xml" are for the database. One then needs to edit the "traccar.xml" configuration file and maybe the "default.xml" configuration file, both found in "/op/traccar/conf". zip into say "/home/user/traccar" gives a shell script ("n"). It is probably wise to make sure that Traccar works before carrying out the integration with OpenGTS. So these notes are for the last Traccar version 4 release (4.15) that is available here. We have not been able to integrate the latest version of of Traccar (version 5.3) with the latest version of OpenGTS (version 2.6.7) since there is a "tc_attributes" error on starting the Traccar server when it is configured to use an OpenGTS database. Traccar installation a) InstallationĪs explained, the Traccar installer package (for Linux 圆4 and other systems) can be downloaded from. These implementation notes are for Ubuntu 18.04 LTS on HPE ProLiant DL20 Gen10 servers. However, several issues arise so it is probably useful to summarise how to install and integrate self-hosted instances of OpenGTS and Traccar. In the case of Jura Mountains' mapping, being able to monitor the routes one actually followed in exploring historic paths and tracks allows us to check the accuracy of the JuraMap map. It is therefore useful to integrate Traccar with OpenGTS. The Traccar open-source web-based GPS tracking system works with a broader range of GPS clients and protocols and the Traccar Client works with recent versions of Android. However, the mGTS mobile phone client for OpenGTS only works with older versions of Android (a Nexus 5 phone running Android version 6.0.0 in our case). The open-source OpenGTS web-based GPS tracking system is well established and allows the detailed management of tracking devices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |