https://development.agtek.com/dokuwiki/ 2026-08-09T07:58:43+0000 https://development.agtek.com/dokuwiki/ https://development.agtek.com/dokuwiki/lib/tpl/dokuwiki/images/favicon.ico text/html 2012-10-10T16:17:17+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:access_file_permissions&rev=1349885837&do=diff Overview AGTEK Access as originally imagined did not have permissions associated with files and folders. If a user account existed for a company and is successfully authenticated, that user has permissions on all files and folders for that company. The intent was to keep AGTEK Access as simple as possible for the end user and avoid the complexity that permissions systems can introduce. text/html 2013-04-05T19:02:10+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:access_server_2013_robustification_project&rev=1365188530&do=diff Access Server 2013 Robustification Project The Access/License server has been running fine for several years but it has become apparent that the system is vulnerable to some “single point of failure” conditions. Problems There are many potential problems with the current Access server architecture. In a rough order of severity they are: text/html 2015-08-31T23:15:50+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:access_server_2015_maintenance&rev=1441062950&do=diff Sprint 5A - 2015 Maintenance Start 2015-04-10 Task Number Owner Estimate Actual Status Description 5.2 WebApplcation 5.2.1 Mike A 0.0 Done Add “.kml” to track download text/html 2012-10-10T17:05:10+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:access_server_database_schema&rev=1349888710&do=diff Access Server Database Schema The Access Server contains two database schemas. One for the “master” database and one for each “customer” database. Master Database The Access Server has one master database that contains all data that needs to be accessed without knowing the customer context. This includes the list of customers, the list of users, TMM configuration and device assignment. All data that belongs to a specific customer is placed in the customer database. The list of users may seem … text/html 2014-10-16T00:20:16+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:access_server_track_system_merge&rev=1413418816&do=diff October Suprise Earlier track system work for 2014 was completed here: Most of the track work needed to be integrated into the trunk code line and then deployed. For October/November 2014 an Access Project is as follows: * Merge Access Track 1.20 into the trunk. text/html 2018-10-25T17:50:34+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:access_software_tags&rev=1540489834&do=diff Access Software Subversion Tags NOTE: These tags are no longer maintained, see the build instructions for the server. Jenkins Build System The following is a list of Subversion tags and the associated software versions. Date Subversion Tag Access Server Access Client text/html 2012-10-10T17:09:22+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:access_software_testing&rev=1349888962&do=diff Access Software Testing The entire AgtekNet software suite is built and tested on a nightly basis. The nightly build and unit tests are run on the development machine dev.agtek.com from the mdm account. The build is scheduled to run at midnight using cron, and executes the script: text/html 2012-10-10T16:54:09+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:access_subversion_tags&rev=1349888049&do=diff = Access Server Subversion Tags = text/html 2013-10-29T15:54:57+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:access_web_application&rev=1383062097&do=diff Introduction NOTE: Tasks 1-4 have been incorporated into the Trackwork 2013 ecosystem The AGTEK Access Web application provides simple administration capabilities to customer administrators without the need to be AGTEK Earthworks users. The basic application provides the ability to add / modify / delete users, and perform limited administration of LicenseKey instances. LicenseKeys can be modified to add or remove users, or change the amount of time a LicenseKey may be checked out. text/html 2018-10-02T16:59:54+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agtek_access_and_license_server&rev=1538499594&do=diff This catchall section describes various aspects of the AGTEK Access file and license server solution. Access File Permissions Setting up a new AWS VPC Current Design: * Access Server Database Schema * AGTEKNet Repository Layout * Internet Key System * Project Journal Software Infrastructure: * AgtekNet Package Descriptions * Access Software Testing * Running C++ Unit tests on Windows. * LicenseKey Programming Patterns Projects: * Project Hydra * Server 2017 Increme… text/html 2012-10-10T22:09:30+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agtek_access_applications&rev=1349906970&do=diff Main Page Control Files Control is a critical part of GPS on a job site. It should not change except with great forthought and checking. The most likely reason for it to change is on a job that requires multiple base setups. Apps doing alignment can upload to AGTEK Access projects and store a control file with a description. Apps that can use alignment data can check AGTEK Access for control files when none is present in their file. text/html 2018-12-04T17:01:04+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agtek_access_c_api&rev=1543942864&do=diff AccessLib C++ API The AGTEK Access Server provides networked storage for AGTEK customer project data including GPS devices, project definitions, vehicle lists, vehicle-device associations, GPS track data and shared file storage. The AccessLib C++ API text/html 2018-10-19T21:39:55+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agtek_access_dev&rev=1539985195&do=diff AGTEK Access Server Development This note describes the state of the AGTEK Access Server development environment as of October 2018. All the server code is written in Java 1.8 and doesn't use any newer language features. In fact 1.8 features are pretty limited to a few instances of lamdas here and there. text/html 2018-10-31T21:24:57+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agtek_access_future&rev=1541021097&do=diff Introduction This page details possible items for implementation on the Access server. Possible Problems to keep an eye on * Distributed lock manager occasionally has file stores fail because “item not locked for read” * A server (Production-A, I think) fell over on October 17, 2018 with text/html 2019-08-01T16:08:32+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agtek_access_security_-_user_roles&rev=1564675712&do=diff Access Security - User Roles text/html 2019-08-02T17:59:20+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agtek_tracker_proxy_server&rev=1564768760&do=diff Agtek Tracker Proxy Server A server was created to support capturing tracks from the new CalAmp Trackers. These trackers use a UDP based protocol to send data to the server. Adding this capability to the existing Access server was determined to be risky at best and may not have even been possible. A dedicated server was created which acts as a proxy server for getting the track data to the Access Server. When track data is received it is captured and forwarded to Access using the existing Ac… text/html 2013-11-22T17:13:56+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agteknet_package_descriptions&rev=1385140436&do=diff AgtekNet Package Descriptions The following sections summarize all the java source code packages checked into subversion as part of the AgtekNet repository. com.agtek.net.access.client.* The package and sub-packages implementing the AGTEK Access Client java application. text/html 2012-10-10T17:06:28+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agteknet_repository_layout&rev=1349888788&do=diff AgtekNet Repository Layout The AgtekNet repository contains the java source code, documentation and build and distribution scripts for all the java based Access server and client applications. The repository is stored in the subversion server running on w2kserver2, and can be checked out with the following command: text/html 2018-10-19T18:54:03+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:agtel_access_server_operations&rev=1539975243&do=diff Introduction This note details some of the operational aspects of the Access server. Ultimately this can not cover every aspect of the server and it's not within the capabilities of AGTEK R&D to document things very deeply. The best reference of the server operational behavior is the code base. text/html 2012-10-10T17:08:22+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:amazon_cloud_computing&rev=1349888902&do=diff Amazon Cloud Computing I just spent about a day and half working with various Amazon Cloud Computing products to investigate the possibility of moving Agtek's server offerings out of our facility and into Amazon's Cloud. As it's the day before Thanksgiving I thought I'd document all my findings so that when I come back to work next week there will be a record. text/html 2012-10-10T17:08:37+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:amazon_s3_cost_scenarios&rev=1349888917&do=diff Main Page S3 Cost Scenarios Worst Case Assumptions * 10 Users, 1 Gb per user, shared space of 10 Gb * The 10 Gb of space will change over the year by 50% per month of actual uploads * Each of the 10 users will download the 15 Gb of uploads for 150 Gb of downloads text/html 2016-07-13T00:36:50+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:cpp_track_api&rev=1468370210&do=diff C++ API for tracking The C++ API contains the TrackAPI, which is useful for tracking applications. There isn't a lot of functionality, and the API is minimal in order to accomplish base tasks. It is possible that this API is extended in the future (e.g. later than mid-2015). text/html 2020-08-06T20:10:24+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:file_directory_sync_algorithm&rev=1596744624&do=diff Keeping Files and Directories in Sync with Access Moving forward we will want to keep selected local Projects in sync with Access. It should be possible for a user to manage projects locally on the desktop. This can be done using the Windows File Explorer or by using the Agtek Application Framework. If using the File Explorer the changes will only be visible locally. When the user launches the Agtek Application Framework and connects with Access any local changes will be able to be synchro… text/html 2012-10-10T16:20:52+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:internet_key_api_development&rev=1349886052&do=diff Summary This page details the functionality of the AGTEK Access Internet Key system. The syntax of these operations is pseudo object oriented, with a some English prose to indicate parameter and return types. This should not be taken as a real programmer's documentation, but rather as a specification indicating how the text/html 2012-10-10T16:20:16+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:internet_key_model&rev=1349886016&do=diff Summary This page describes the abstract, the concrete client, and the DB model used for the key system. This page does not describe the generic program flow and operations required to implement all features. It may describe certain operations particularly where SQL queries are needed to perform operations. text/html 2017-10-31T16:47:31+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:internet_key_stories&rev=1509468451&do=diff Release Contents All stories (0-3) comprise this first release. It includes the internet keys (permanent, timed, and rental) for Windows desktops and android phone support. This is in fact the bulk of the product. Pieces that may be left out for this release are some reporting (some are critical like Rental reports). It does not require one time keys (ala' authorizations) or software keys (once a year authorization) for this release. We will be running in parallel with the Solo Server at this t… text/html 2012-10-10T16:19:00+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:internet_key_system&rev=1349885940&do=diff Internet Key Copy Protection A moving outline of what the existing key system does, its deficiencies, and additions needed for the new system. This page serves as the “landing page” for all things “key-related”. You may need to visit these sub pages in order to get a more detailed look at the work. text/html 2012-10-10T16:20:04+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:internet_key_tasks&rev=1349886004&do=diff Story 0 - Foundation Start 2011-01-17 Task Number Owner Estimate Actual Status Description 0.1 M & M 1 1 Done Develop stories, task lists, estimates 0.2 Mike A 1 1 Done AGTEK Access familiarization, development setup text/html 2012-10-10T16:18:29+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:internet_key_vision&rev=1349885909&do=diff Description Internet keys are a copy protection method that allows software to be loaded on many devices but run simultaneously only up to the number of keys purchased. A company might have 10 users but only 4 keys so only 4 users could run the software at once. This is very similar to a seat license arrangement. text/html 2018-06-26T22:22:29+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:journal-file-proposal&rev=1530051749&do=diff Journal File Storage Project journal items are obtained from field data and may either post processed from KMZ data or may be stored proactively by field (mobile) applications. As noted in the Access Web 2.0 story, project journals are composed of the four types of data entries: text/html 2012-10-10T16:20:30+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:key_tamper_detection&rev=1349886030&do=diff Summary To prevent a key from being checked out, then copied, the key is fingerprinted with various pieces of system information. These fingerprint values are later checked to make sure that the system currently running is largely the same as it was before. Some changes are allowed, in case the user needs to update parts of their hardware (memory, disk, etc). Some of the parameters (listed in the next section) are not appropriate for all platforms. The selection of platform parameters is depend… text/html 2018-11-07T17:34:09+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:licensekey-rework-2018&rev=1541612049&do=diff Forced Update Revisions 9-28-2018 Revision 1 Desktop * Add Export - Sitework 3D compatible file function instead of using IP Grid Compatible * Check for Update to be run on program start - also user command on Help - Check for Updates * Requires checking with server for version text/html 2019-05-09T20:03:20+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:licensekey-reworkd-2018-tasks&rev=1557432200&do=diff Story LicenseKeyRefactor18 (LKR18) - Support LicenseKey fixes for the desktop Start 2018-10-02 Task Number Owner Actual Estimate Status Description Notes text/html 2016-07-19T15:16:18+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:licensekeyprogrammingpatterns&rev=1468941378&do=diff TB developed 2016-07-19 text/html 2017-03-30T21:46:09+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:new_aws_vpc&rev=1490910369&do=diff How to set up a new VPC in AWS for testing or production These instructions indicate how to create a new VPC for an AGTEK Access server. This is useful for either testing, or migration of an entirely new constellation of server components. These instructions do not indicate how to add multiple EC2 instances to the VPC for load balancing or failover error recovery. text/html 2017-11-20T17:32:15+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:project_journal&rev=1511199135&do=diff Project Journal The :Project Journal“ (journal) is a new feature for the Agtek Access server. The journal will record events related to the project. This enabled applications to timeline of events related to the project. Here are some example of data items to be stored: text/html 2017-11-21T01:35:07+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:server2017tasks&rev=1511228107&do=diff Story 7.B - 2017 Server Incremental Work This is a “new” 7.B, with changes to support the AccessWeb application and website integration. Server and API to be renamed to 1.25.2. Start 2017-10-24 Task Number Owner Actual Estimate text/html 2018-06-04T23:54:31+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:server2018q1tasks&rev=1528156471&do=diff Story 8 - 2018 Q1 Multiheader server robustification - Project Hydra Start 2018-03-07 Task Owner State Estimate Actual Description Notes text/html 2014-02-26T23:14:48+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:track2013stories&rev=1393456488&do=diff AGTEK Access Server - Trackwork 2013 To support SmartTrack and Trackwork applications, the AGTEK Access server needs to change to accommodate new requirements. The first version of the server, written by external consultants, was a C++/Linux based server which had several issues. The second version of the server, written in Java/Linux, has been in production since 2009. A modified server implementation starting in 2014 is anticipated to support the track applications. text/html 2014-03-11T00:15:30+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:track2013tasks&rev=1394496930&do=diff Story 1 Interface & Flow Start 2013-10-25 Task Number Owner Actual Estimate Status Description 1.1 0 0 Done Tag AgtekNet for pre-track work 1.2 0 text/html 2017-01-25T00:40:10+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:track2016tasks&rev=1485304810&do=diff Story 4 Server Reachitecture Start 2013-07-08 Task Number Owner Actual Estimate Status Description 3.1 Distributed Lock Manager 3.1.1 3 5 text/html 2015-12-01T00:45:34+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:track_labeling&rev=1448930734&do=diff Track Labeling Some early tracking customers have indicated that they want to label tracks with arbitrary information, job specific information. Examples of this may be “gravel”, “topsoil”, or “cut”, “fill”. These labels are not only job specific, but customer (AKA contractor) specific. text/html 2016-12-22T18:37:34+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:track_statistics_definitions&rev=1482431854&do=diff The following statistics are computed from various track. The meanings and definitions of each statistic is as follows: * Track_Line: The connected line of locations along a single track * Travel: The total length of the track from the first point to the last point. text/html 2016-07-13T00:37:59+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:trackwork_archive&rev=1468370279&do=diff AGTEK SmartTrack SmartTrack Stories SmartTrackTasks AGTEK JobSite Manager JobSite Manager Stories JobSiteManagerTasks Trackwork Server V1 (C++/Linux) Discussion of the existing Linux/C/MySql based server. Trackwork Server Detailed description of the MySql tables used by the existing trackwork server. Trackwork Server Tables Historical Trackwork components text/html 2012-10-10T17:11:04+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:trackwork_client_api&rev=1349889064&do=diff Access Server Client API Currently the trackwork server and the file storage server are accessed through separate APIs. The new Access Server will combine both pieces of functionality into one client side API. Feature Requirements * Single authentication for all APIs including: text/html 2012-10-10T17:12:26+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:trackwork_server&rev=1349889146&do=diff Trackwork Server This page is intended for discussion of the Trackwork Server with a focus on issues and concerns of scalability, performance, maintenance and day to day operations. Scalability After a few weeks of testing with the Vasco Road/Teichert job we are closing in on 3 million GPS data points all in one database table. It makes me wonder how the product will scale if we have several of these jobs running in parallel on several systems. Since all the GPS data lives in the database it… text/html 2018-09-18T23:10:15+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:trackwork_server_existing_and_future&rev=1537312215&do=diff Trackwork System Future Trackwork Server (aka Access Server) This landing page is the “one stop shop” for all things track related. The historical archives contain information from the earliest server days, intermediate version, etc. For the most part this page will refer to the current state of the trackwork eco-system. text/html 2012-10-10T17:11:35+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:trackwork_server_tables&rev=1349889095&do=diff Trackwork Server Tables Notes: * Unless otherwise specified all times stored in the database are integer seconds offset from the unix epoch where 0 is January 1, 1970 GMT. Location Table (loc) In the future this table should go away and be replaced with device/day based file system for scalability text/html 2012-10-10T17:12:39+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:trackwork_v.2_feature_requirements&rev=1349889159&do=diff Required Features * Store GPS points * Send and Retrieve GPS Points (Autonomous or RTK) * Create representative summary view for app (tracks, both TMM like device and RTK) * Administration utilities (backup, migration, archive, restore, add customer, delete customer, shipping delivery mechanism (ie: generating xml authentication file if necessary) text/html 2015-08-28T18:30:54+0000 Anonymous (anonymous@undisclosed.example.com) https://development.agtek.com/dokuwiki/doku.php?id=access:windows_cpp_unit_tests&rev=1440786654&do=diff The C++ version of the AccessLib API is provided with a base set of Google Test unit tests. Running these on Windows requires a fair amount of setup. The C++ unit tests are relying upon a running server, with some presupplied data (from the Java Unit Tests). The server should be run from Eclipse on the same machine as the unit tests, but needs to connect to the same MySQL instance used in the Java Unit Tests (usually dev.agtek.com).