Sitewhere Versions Save

SiteWhere is an industrial strength open-source application enablement platform for the Internet of Things (IoT). It provides a multi-tenant microservice-based infrastructure that includes device/asset management, data ingestion, big-data storage, and integration through a modern, scalable architecture. SiteWhere provides REST APIs for all system functionality. SiteWhere provides SDKs for many common device platforms including Android, iOS, Arduino, and any Java-capable platform such as Raspberry Pi rapidly accelerating the speed of innovation.

v3.0.5

3 years ago

Maintenance Release

This is a maintenance release. For a list of issues addressed, see the release notes here.

In order to deploy 3.0.5 with swctl use version 0.9.2.

v3.0.4

3 years ago

Maintenance Release

This is a maintenance release. For a list of issues addressed, see the release notes here.

In order to deploy 3.0.4 with swctl use version 0.7.0 or later.

v3.0.3

3 years ago

Maintenance Release

This is a maintenance release. For a list of issues addressed, see the release notes here.

In order to deploy 3.0.3 with swctl use version 0.4.5 or later.

v3.0.2

3 years ago

Maintenance Release

This is a maintenance release that fixes bugs found in the 3.0.1 release. For a list of issues addressed, see the release notes here.

In order to deploy 3.0.2 with swctl use version 0.4.4 or later.

v3.0.1

3 years ago

Maintenance Release

This is a maintenance release that fixes bugs found in the initial 3.0.0 release. For a list of issues addressed, see the release notes here.

In order to deploy 3.0.1 with swctl use version 0.4.2.

v3.0.0

3 years ago

This is the first release of the SiteWhere 3.0 platform, which introduces a new cloud-native architecture with more comprehensive Kubernetes integration. As part of the 3.0 release plan, the SiteWhere team is developing a new website/documentation hub. This is a work in progress, but the latest content is available at:

https://next.sitewhere.io/docs/

sitewhere-3.0.0-beta1

3 years ago

Beta Notice

This is the first beta release for SiteWhere 3.0 which introduces a number of architectural updates and moves toward a "cloud native" approach for the platform. Because this is beta software, you can expect to run into bugs, which you can report via GitHub issues.

New Features

Kubernetes Integration

SiteWhere 3.0 is designed with a microservice architecture and is intended to be run on Kubernetes. Many aspects of the system have been refactored to "play well" in the k8s ecosystem including:

  • Deployment - A new utility, swctl has been introduced to make deployment easier. Both the required infrastructure and system microservices can be easily deployed with a couple of commands. Helm charts are still available for manually installing the system components.
  • Custom Resources - Custom resources (CRDs) are used to represent many of the core SiteWhere entities such as instances, tenants, and microservices. System configuration can easily be viewed using standard k8s tooling such as kubectl.
  • Microservice Operator - A Kubernetes operator is used to control how microservices are translated into deployments/services as well as the deployment of system tenants and configuring tenant engines for each microservice/tenant combination.

Oracle GraalVM Support

SiteWhere 3.0 uses Quarkus as the basis for its microservice library. Spring Boot and other dependencies have been removed and replaced with more lightweight implementations compatible with Quarkus. The end goal is to compile all SiteWhere microservices to native images for a smaller footprint and faster startup times. This beta release still generates JVM bytecode with a larger footprint, but GA will run on native images.

Relational Database Support

SiteWhere 3.0 separates data into two categories, master data and event data. Master data includes definitions of core entities such as devices, device types, assets, device assignments, etc and is well-suited for relational modeling. The initial release deploys master data to PostgreSQL while defaulting to InfluxDB for time series event data.

Redis Distributed Caching

The infrastructure now includes an HA Redis deployment which is used by all microservices to cache information and improve performance compared to requiring gRPC calls to share information between microservices.

There are many other new features and architectural improvements in this release. The SiteWhere team will release documentation as we move toward a GA release.

sitewhere-2.1.1

3 years ago

This is an enhancement & bug fix release.

Enhancements

  • Added Update User logic (#802)

Bug Fixes

sitewhere-2.1.0

4 years ago

This is an major release for SiteWhere CE 2.1.0 which introduces many new architectural features and some API updates.

New Features

  • Integrate Istio as service mesh for SiteWhere microservices (#713)
  • Create Apache Syncope user management implementation (#724)
  • Support multiple concurrent assignments per device (#750)

Enhancements

  • Make MongoDB log level configurable via environment (#719)
  • Combine user/tenant management into instance management microservice (#723)
  • Allow gRPC exponential backoff settings to be set via environment (#728)
  • Use exponential backoff for Zookeeper bootstrap indicator checks (#730)
  • Use Kafka rather than gRPC for transmitting inbound events for storage (#733)
  • Convert metrics gathering code to use Prometheus (#735)
  • Create lifecycle component for bootstrapping tenant engines (#736)
  • Add HTTP endpoint for acquiring Prometheus metrics (#743)
  • Support retrieving areas/customers as tree structures via REST services (#745)
  • Include tenant management API in all microservices (#752)
  • Device type relations should have tokens unique within device type (#755)
  • Move MongoDB index creation into a separate background thread (#767)

Bug Fixes

  • State change updates sending after shutdown and throwing exceptions (#726)
  • MongoDB server selection timeout exceeded (#721)
  • Allow clients to choose between cached/uncached data for remote APIs (#757)
  • Batch element processed date always displays as null (#769)
  • Do not put artificial limits on event date ranges if not entered (#774)

sitewhere-2.1.beta1

4 years ago

This is an beta release for SiteWhere CE 2.1.0 which introduces many new architectural features.

New Features

  • Integrate Istio as service mesh for SiteWhere microservices (#713)
  • Create Apache Syncope user management implementation (#724)

Enhancements

  • Convert metrics gathering code to use Prometheus (#735)
  • Create lifecycle component for bootstrapping tenant engines (#736)
  • Use Kafka rather than gRPC for transmitting inbound events for storage (#733)
  • Use exponential backoff for Zookeeper bootstrap indicator checks (#730)
  • Allow gRPC exponential backoff settings to be set via environment (#728)
  • Combine user/tenant management into instance management microservice (#723)
  • Make MongoDB log level configurable via environment (#719)

Bug Fixes

  • State change updates sending after shutdown and throwing exceptions (#726)
  • MongoDB server selection timeout exceeded (#721)