Skip to content

Releases: Geotab/mygeotab-api-adapter

v2.2.0.2

23 Apr 14:21
@sdietz888 sdietz888
v2.2.0.2
8f3774d
Compare
Choose a tag to compare
v2.2.0.2 Latest
Latest

Notes

  • Self-contained deployments are packaged in zip files - the names of which are prefixed with "MyGeotabAPIAdapter_SCD_" (for the MyGeotab API Adapter) or "MyGeotabAPIAdapter.DataOptimizer_SCD_" (for the MyGeotab API Adapter Data Optimizer) followed by the target Runtime Identifier (e.g. "win-x64").
  • If using SQL Server or Azure SQL for the adapter database, the SQLServer.zip file contains the scripts associated with this release.
  • If using PostgreSQL for the adapter database, the PostgreSQL.zip file contains the scripts associated with this release.
  • If using Oracle for the adapter database, the Oracle.zip file contains the scripts associated with this release.
  • For the Data Optimizer database, the SQLServer_DataOptimizer.zip file contains the scripts associated with this release.

The following resources are available for further information:

Changes This Release

Changes to the API Adapter and Data Optimizer are listed in the sections below. NOTE: There are no database schema or configuration file changes from version 2.2.0 to version 2.2.0.2. It is safe to upgrade from version 2.2.0 to version 2.2.0.2 by simply downloading the new version and overwriting the respective appsettings.json file(s) with those that were configured for version 2.2.0.

API Adapter

  • NOTE: There are no database schema or configuration file changes from version 2.2.0 to version 2.2.0.2. It is safe to upgrade from version 2.2.0 to version 2.2.0.2 by simply downloading the new version and overwriting the respective appsettings.json file(s) with those that were configured for version 2.2.0.
  • Modified the optional minimum interval sampling capability for LogRecord and StatusData feeds to accommodate older data:
    • See the Minimum Interval Sampling section in this guide for more information.
    • Primarily designed for use cases such as mining and other remote operations where vehicles may be outside of cellular reception for days or weeks at a time while occasional data points are received via IOX-SATIRDv2.
    • Added GeotabDateTimeProviderComparer to facilitate sorting of Geotab entities based on their DateTime values.
    • Modified MinimumIntervalSampler class to:
      • sort batches of LogRecords or StatusData entities by DateTime prior to applying minimum interval sampling logic.
      • “reset” the tracked DateTime for the subject DeviceId (for LogRecord entities) or DeviceId + DiagnosticId (for StatusData entities) upon encountering older entities within batches being processed.
  • Modified DatabaseResilienceHelper to retry on "Connection is busy" exceptions.
  • Updated NuGet packages to the latest stable release.
  • Updated version to 2.2.0.2.

For information on changes introduced in earlier releases, please refer to the Change Log section in the MyGeotab API Adapter - Solution and Implementation Guide.

Data Optimizer

  • NOTE: There are no code or database changes in this release. Updates other than those noted below are restricted to the API Adapter.
  • Modified DatabaseResilienceHelper to retry on "Connection is busy" exceptions.
  • Updated NuGet packages to the latest stable release.
  • Updated version to 2.2.0.2.

For information on changes introduced in earlier releases, please refer to the Change Log section in the MyGeotab API Adapter - Data Optimizer - Solution and Implementation Guide.

Assets 14

v2.2.0

17 Apr 20:07
@sdietz888 sdietz888
v2.2.0
2095f3f
Compare
Choose a tag to compare
v2.2.0

Notes

  • Self-contained deployments are packaged in zip files - the names of which are prefixed with "MyGeotabAPIAdapter_SCD_" (for the MyGeotab API Adapter) or "MyGeotabAPIAdapter.DataOptimizer_SCD_" (for the MyGeotab API Adapter Data Optimizer) followed by the target Runtime Identifier (e.g. "win-x64").
  • If using SQL Server or Azure SQL for the adapter database, the SQLServer.zip file contains the scripts associated with this release.
  • If using PostgreSQL for the adapter database, the PostgreSQL.zip file contains the scripts associated with this release.
  • If using Oracle for the adapter database, the Oracle.zip file contains the scripts associated with this release.
  • For the Data Optimizer database, the SQLServer_DataOptimizer.zip file contains the scripts associated with this release.

The following resources are available for further information:

Changes This Release

Changes to the API Adapter and Data Optimizer are listed in the sections below. NOTE: This build includes changes to the API Adapter appsettings.json configuration file.
To upgrade an existing installation of the MyGeotab API Adapter solution from version 2.1.4 to version 2.2.0, see the MyGeotab API Adapter — Upgrade Guide — from v2.1.4 to v2.2.0.

API Adapter

  • NOTE: This build includes changes to the API Adapter appsettings.json configuration file.
    To upgrade an existing installation of the MyGeotab API Adapter solution from version 2.1.4 to version 2.2.0, see the MyGeotab API Adapter — Upgrade Guide — from v2.1.4 to v2.2.0.
  • Added optional minimum interval sampling capability for LogRecord and StatusData feeds:
    • See the Minimum Interval Sampling section in this guide for more information.
      Added “EnableMinimunIntervalSamplingForLogRecords”, “EnableMinimunIntervalSamplingForStatusData”,
    • “MinimumIntervalSamplingDiagnostics” and “MinimumIntervalSamplingIntervalSeconds” settings to the API Adapter appsettings.json file.
    • Added MinimumIntervalSampler class.
    • Updated AdapterConfiguration, LogRecordProcessor, StatusDataProcessor, Program.cs and appsettings.json files.
  • Updated NuGet packages to the latest stable release.
  • Updated version to 2.2.0.

For information on changes introduced in earlier releases, please refer to the Change Log section in the MyGeotab API Adapter - Solution and Implementation Guide.

Data Optimizer

  • NOTE: There are no code or database changes in this release. Updates other than those noted below are restricted to the API Adapter.
  • Updated NuGet packages to the latest stable release.
  • Updated version to 2.2.0.

For information on changes introduced in earlier releases, please refer to the Change Log section in the MyGeotab API Adapter - Data Optimizer - Solution and Implementation Guide.

Assets 14
Loading

v2.1.4

05 Apr 17:35
@sdietz888 sdietz888
v2.1.4
6bb29c6
Compare
Choose a tag to compare
v2.1.4

Notes

  • Self-contained deployments are packaged in zip files - the names of which are prefixed with "MyGeotabAPIAdapter_SCD_" (for the MyGeotab API Adapter) or "MyGeotabAPIAdapter.DataOptimizer_SCD_" (for the MyGeotab API Adapter Data Optimizer) followed by the target Runtime Identifier (e.g. "win-x64").
  • If using SQL Server or Azure SQL for the adapter database, the SQLServer.zip file contains the scripts associated with this release.
  • If using PostgreSQL for the adapter database, the PostgreSQL.zip file contains the scripts associated with this release.
  • If using Oracle for the adapter database, the Oracle.zip file contains the scripts associated with this release.
  • For the Data Optimizer database, the SQLServer_DataOptimizer.zip file contains the scripts associated with this release.

The following resources are available for further information:

Changes This Release

Changes to the API Adapter and Data Optimizer are listed in the sections below. NOTE: This build includes changes to the schema of the adapter database and appsettings.json file.
To upgrade an existing installation of the MyGeotab API Adapter solution from version 2.1.3 to version 2.1.4, see the MyGeotab API Adapter — Upgrade Guide — from v2.1.3 to v2.1.4.

API Adapter

*NOTE: This build includes changes to the schema of the adapter database and appsettings.json file.
To upgrade an existing installation of the MyGeotab API Adapter solution from version 2.1.3 to version 2.1.4, see the MyGeotab API Adapter — Upgrade Guide — from v2.1.3 to v2.1.4.

  • Added a new DutyStatusLogs table to the adapter database along with an associated configurable DutyStatusLogProcessor to provide the ability to extract DutyStatusLog (HOS) data from the MyGeotab database.
  • Updated the DatabaseResilienceHelper to handle PostgreSQL-specific connection exceptions with retry logic.
  • Updated all other NuGet packages to the latest stable release.
  • Updated version to 2.1.4.

For information on changes introduced in earlier releases, please refer to the Change Log section in the MyGeotab API Adapter - Solution and Implementation Guide.

Data Optimizer

  • NOTE: There are no code or database changes in this release. Updates other than those noted below are restricted to the API Adapter.
  • Updated the DatabaseResilienceHelper to handle PostgreSQL-specific connection exceptions with retry logic.
  • Updated all other NuGet packages to the latest stable release.
  • Updated version to 2.1.4.

For information on changes introduced in earlier releases, please refer to the Change Log section in the MyGeotab API Adapter - Data Optimizer - Solution and Implementation Guide.

Assets 14
Loading

v2.1.3

28 Feb 20:30
@sdietz888 sdietz888
v2.1.3
21c8fbc
Compare
Choose a tag to compare
v2.1.3

Notes

  • Self-contained deployments are packaged in zip files - the names of which are prefixed with "MyGeotabAPIAdapter_SCD_" (for the MyGeotab API Adapter) or "MyGeotabAPIAdapter.DataOptimizer_SCD_" (for the MyGeotab API Adapter Data Optimizer) followed by the target Runtime Identifier (e.g. "win-x64").
  • If using SQL Server or Azure SQL for the adapter database, the SQLServer.zip file contains the scripts associated with this release.
  • If using PostgreSQL for the adapter database, the PostgreSQL.zip file contains the scripts associated with this release.
  • If using Oracle for the adapter database, the Oracle.zip file contains the scripts associated with this release.
  • For the Data Optimizer database, the SQLServer_DataOptimizer.zip file contains the scripts associated with this release.

For more information, please refer to the MyGeotab API Adapter presentation, the MyGeotab API Adapter - Solution and Implementation Guide, the MyGeotab API Adapter and Data Optimizer presentation and the MyGeotab API Adapter - Data Optimizer - Solution and Implementation Guide.

Changes This Release

Changes to the API Adapter and Data Optimizer are listed in the sections below. NOTE: There are no database schema or configuration file changes from version 2.1.2 to version 2.1.3. It is safe to upgrade from version 2.1.2 to version 2.1.3 by simply downloading the new version and overwriting the respective appsettings.json file(s) with those that were configured for version 2.1.2.

API Adapter

*NOTE: There are no database schema or configuration file changes from version 2.1.2 to version 2.1.3. It is safe to upgrade from version 2.1.2 to version 2.1.3 by simply downloading the new version and overwriting the respective appsettings.json file(s) with those that were configured for version 2.1.2.

  • Updated the solution from .NET 6.0 to .NET 8.0.
  • Removed ubuntu2004-x64 publish profiles due to breaking change caused by smaller RID graph in .NET 8 (see https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/8.0/rid-graph)
  • Updated Geotab.Checkmate.ObjectModel from version 11.6.171 to 11.7.179.
  • Updated all other NuGet packages to the latest stable release.
  • Updated version to 2.1.3.

For information on changes introduced in earlier releases, please refer to the Change Log section in the MyGeotab API Adapter - Solution and Implementation Guide.

Data Optimizer

*NOTE: There are no database schema or configuration file changes from version 2.1.2 to version 2.1.3. It is safe to upgrade from version 2.1.2 to version 2.1.3 by simply downloading the new version and overwriting the respective appsettings.json file(s) with those that were configured for version 2.1.2.

For information on changes introduced in earlier releases, please refer to the Change Log section in the MyGeotab API Adapter - Data Optimizer - Solution and Implementation Guide.

Assets 14
Loading