\ No newline at end of file
diff --git a/blog/index.xml b/blog/index.xml
index 9b8595b..d7e3a0b 100644
--- a/blog/index.xml
+++ b/blog/index.xml
@@ -1 +1 @@
-Blog on WLDThttps://wldt.github.io/blog/Recent content in Blog on WLDTHugo -- gohugo.ioenCopyright (c) 2023 HyasThu, 07 Sep 2023 16:21:44 +0200ls WLDT Library Version 0.3.0https://wldt.github.io/blog/ls-wldt-library-version-0.3.0/Wed, 13 Mar 2024 16:27:22 +0200https://wldt.github.io/blog/ls-wldt-library-version-0.3.0/📣 We’re thrilled to announce the release of version 0.3.0 of the White Label Digital Twins (WLDT) library! This release brings significant enhancements, improvements, and new features to further empower developers in designing, developing, and deploying Digital Twins within Internet of Things (IoT) ecosystems.
\ No newline at end of file
+Blog on WLDThttps://wldt.github.io/blog/Recent content in Blog on WLDTHugo -- gohugo.ioenCopyright (c) 2023 HyasThu, 07 Sep 2023 16:21:44 +0200WLDT Library Version 0.4.0https://wldt.github.io/blog/wldt-library-version-0.4.0/Thu, 29 Aug 2024 17:40:54 +0200https://wldt.github.io/blog/wldt-library-version-0.4.0/We’re excited to announce the release of WLDT version 0.4.0! This update brings powerful new features to enhance your Digital Twin (DT) experience, including event observation capabilities, a robust storage layer, and a flexible query system.WLDT Library Version 0.3.0https://wldt.github.io/blog/wldt-library-version-0.3.0/Wed, 13 Mar 2024 16:27:22 +0200https://wldt.github.io/blog/wldt-library-version-0.3.0/📣 We’re thrilled to announce the release of version 0.3.0 of the White Label Digital Twins (WLDT) library! This release brings significant enhancements, improvements, and new features to further empower developers in designing, developing, and deploying Digital Twins within Internet of Things (IoT) ecosystems.
\ No newline at end of file
diff --git a/blog/sitemap.xml b/blog/sitemap.xml
index fc8204e..23dceb9 100644
--- a/blog/sitemap.xml
+++ b/blog/sitemap.xml
@@ -1 +1 @@
-https://wldt.github.io/blog/ls-wldt-library-version-0.3.0/2024-03-15T10:45:36+01:00monthly0.5
\ No newline at end of file
+https://wldt.github.io/blog/wldt-library-version-0.4.0/2024-09-05T15:02:33+02:00monthly0.5https://wldt.github.io/blog/wldt-library-version-0.3.0/2024-09-05T15:02:33+02:00monthly0.5
\ No newline at end of file
diff --git a/blog/ls-wldt-library-version-0.3.0/index.html b/blog/wldt-library-version-0.3.0/index.html
similarity index 68%
rename from blog/ls-wldt-library-version-0.3.0/index.html
rename to blog/wldt-library-version-0.3.0/index.html
index 125cbca..0f4804e 100644
--- a/blog/ls-wldt-library-version-0.3.0/index.html
+++ b/blog/wldt-library-version-0.3.0/index.html
@@ -1,9 +1,9 @@
-ls WLDT Library Version 0.3.0 | WLDT
📣 We’re thrilled to announce the release of version 0.3.0 of the White Label Digital Twins (WLDT) library!
This release brings significant enhancements, improvements, and new features to further empower developers in designing, developing, and deploying Digital Twins within Internet of Things (IoT) ecosystems.
For detailed information about these changes and their impact, please refer to the information provided:
Let’s dive into the key changes and updates included in this release:
Migration Digital Adapters
In version 0.3.0, we’ve made several enhancements and adjustments to the Digital Adapter class to improve its functionality and usability. Notable changes include:
Discontinued Methods: Several methods have been discontinued and removed from the DigitalAdapter class to streamline its interface and improve clarity.
Method Signature Changes: The signatures of certain methods have been updated for consistency and clarity, ensuring a more intuitive developer experience.
New Methods: We’ve introduced new methods to provide additional functionality and flexibility for handling state updates and event notifications.
Migration Shadowing Function
We’ve made significant improvements to the ShadowingModelFunction, which is now renamed to ShadowingFunction. Additionally, we’ve introduced changes to how the DigitalTwinState is managed within the Shadowing Function, providing developers with more control and flexibility.
Migrating WLDT Engine & DT Creation
In version 0.3.0, the WldtEngine class has been renamed to DigitalTwin, offering improved clarity and consistency. We’ve also made adjustments to the lifecycle management of Digital Twins, streamlining the process and enhancing usability.
Digital Twin & Digital Twin Engine
We’ve introduced enhancements to the Digital Twin and Digital Twin Engine classes, providing developers with improved functionality and ease of use. Notable updates include:
Simplified Digital Twin Creation: Creating and managing Digital Twins is now more intuitive and streamlined.
Lifecycle Management: We’ve enhanced the lifecycle management of Digital Twins, making it easier to start, stop, and manage multiple instances.
Digital Twin State Manager
The DigitalTwinStateManager class has been improved to provide better support for managing the state of Digital Twins. With features such as transaction support and event notification, developers can more effectively manage changes to Digital Twin states and respond to events.
To learn more about the capabilities of the DigitalTwinStateManager, please refer to the Digital Twin State Manager section.
Digital Adapter
We’ve extended and improved the Digital Adapter base class to provide enhanced support for handling Digital Twin state updates and event notifications. With the introduction of the onStateUpdate and onEventNotificationReceived methods, developers can more effectively respond to changes in Digital Twin states and events.
Get Started with WLDT 0.3.0
To get started with version 0.3.0 of the WLDT library, simply update your dependencies to include the latest release. Detailed documentation and usage examples are available in the project repository, providing comprehensive guidance on leveraging the new features and enhancements.
We’re excited about the improvements and new capabilities introduced in WLDT 0.3.0, and we can’t wait to see how developers utilize them to create innovative IoT solutions powered by Digital Twins. As always, we welcome your feedback and contributions to help us further improve the library and empower the community.
Happy coding with WLDT 0.3.0! 🚀
\ No newline at end of file
diff --git a/blog/wldt-library-version-0.4.0/index.html b/blog/wldt-library-version-0.4.0/index.html
new file mode 100644
index 0000000..2dac31a
--- /dev/null
+++ b/blog/wldt-library-version-0.4.0/index.html
@@ -0,0 +1,7 @@
+
+WLDT Library Version 0.4.0 | WLDT
We’re excited to announce the release of WLDT version 0.4.0! This update brings powerful new features to enhance your Digital Twin (DT) experience, including event observation capabilities, a robust storage layer, and a flexible query system.
For detailed information about these changes and their impact, please refer to the information provided:
WldtEventObserver: A new class has been introduced, simplifying the observation of specific events generated by Digital Twins and their components
Storage Layer: The new storage layer allows DTs to store data related to their state, events, actions, and more. It consists of:
Storage Manager: Manage and use various storage systems (e.g., in-memory, file-based, DBMS) simultaneously.
WldtStorage: An abstract class to implement custom storage systems. The default in-memory storage is available for development and testing.
Query System: The query system enables external components like Digital Adapters to retrieve stored data efficiently, supporting both synchronous and asynchronous queries.
WLDT 0.4.0 significantly enhances the flexibility and capabilities of Digital Twins, making it easier to manage and retrieve data, and observe events. We encourage developers to explore these new features and integrate them into their projects.
Stay tuned for more updates!
+
\ No newline at end of file
diff --git a/docs/adapters/http-digital-adapter/index.html b/docs/adapters/http-digital-adapter/index.html
index 8371e25..ced853c 100644
--- a/docs/adapters/http-digital-adapter/index.html
+++ b/docs/adapters/http-digital-adapter/index.html
@@ -2,23 +2,23 @@
HTTP Digital Adapter | WLDT
The HttpDigitalAdapter is a powerful component designed to facilitate the integration of Digital Twins into HTTP-based systems.
It serves as a bridge between a Digital Twin and HTTP-based applications, allowing developers to easily expose and interact with
-Digital Twin data and functionalities over HTTP.
Key Features:
HTTP Integration: Seamlessly integrates Digital Twins into HTTP environments, enabling communication with web applications and services.
Dynamic Configuration: Offers a flexible configuration mechanism through the HttpDigitalAdapterConfiguration, allowing developers to customize the adapter’s behavior based on specific requirements.
State Monitoring: Monitors changes in the Digital Twin state and provides HTTP endpoints to query the state of the Digital Twin (properties, events, actions and relationships).
Event Notifications: Allows developers to retrieve event notifications triggered by changes in the Digital Twin state.
A complete example is provided in the test folder with a complete DT Creation in the TestMain class together with a demo DT with and emulated Physical Adapter and the HTTP Digital Adapter.
<dependency>
+Digital Twin data and functionalities over HTTP.
Key Features:
HTTP Integration: Seamlessly integrates Digital Twins into HTTP environments, enabling communication with web applications and services.
Dynamic Configuration: Offers a flexible configuration mechanism through the HttpDigitalAdapterConfiguration, allowing developers to customize the adapter’s behavior based on specific requirements.
State Monitoring: Monitors changes in the Digital Twin state and provides HTTP endpoints to query the state of the Digital Twin (properties, events, actions and relationships).
Event Notifications: Allows developers to retrieve event notifications triggered by changes in the Digital Twin state.
Storage & Query: Since version 0.2 the HTTP Digital Adapter is able to retrieve Storage Statistics and execute query on the target DT
A complete example is provided in the test folder with a complete DT Creation in the TestMain class together with a demo DT with and emulated Physical Adapter and the HTTP Digital Adapter.
The HttpDigitalAdapterConfiguration is a crucial part of the HttpDigitalAdapter, providing the necessary settings to
tailor the adapter’s behavior to meet specific needs.
Represents the configuration for an HTTP Digital Adapter, specifying the host, port,
and filters for properties, actions, events, and relationships.
The filters are used to selectively include or exclude specific properties, actions,
@@ -66,6 +66,66 @@
This section of the documentation provides detailed information about the RESTful API exposed by the WLDT - HTTP Digital Adapter.
The API allows you to interact with the Digital Twin (DT) instance, retrieve its state, read properties, actions, event and relationships description,
-and trigger actions.
Available endpoints with the associated methods are:
GET/instance: Retrieves information about the Digital Twin instance.
GET/state: Retrieves the current state of the Digital Twin.
GET/state/changes: Retrieves the list of state changes in the Digital Twin.
GET/state/previous: Retrieves the previous state of the Digital Twin.
GET/state/properties: Retrieves the list of properties in the Digital Twin state.
GET/properties/{propertyKey}: Retrieves the value of a specific property (e.g., /properties/color) from the Digital Twin state.
GET/state/events: Retrieves the list of events in the Digital Twin state.
GET/state/actions: Retrieves the list of actions in the Digital Twin state.
POST/state/actions/{actionKey}: Triggers the specified action (e.g., /state/actions/switch_on) in the Digital Twin state. The raw body contains the action request payload.
GET/state/relationships: Retrieves the list of relationships in the Digital Twin state.
GET/state/relationships/{relationshipName}/instances: Retrieves the instances of the specified relationship (e.g., /state/relationships/insideIn/instances) in the Digital Twin state.
Note: Replace {propertyKey}, {actionKey}, and {relationshipName} with the actual values you want to retrieve or trigger.
-Make sure to use the appropriate HTTP method (GET, POST) and include any required parameters or payload as described in each endpoint’s description. For more detailed information, refer to the Postman Collection for this API available in the folder api: http_adapter_api_postman.json
Available endpoints with the associated methods are:
GET/instance: Retrieves information about the Digital Twin instance.
GET/state: Retrieves the current state of the Digital Twin.
GET/state/changes: Retrieves the list of state changes in the Digital Twin.
GET/state/previous: Retrieves the previous state of the Digital Twin.
GET/state/properties: Retrieves the list of properties in the Digital Twin state.
GET/properties/{propertyKey}: Retrieves the value of a specific property (e.g., /properties/color) from the Digital Twin state.
GET/state/events: Retrieves the list of events in the Digital Twin state.
GET/state/actions: Retrieves the list of actions in the Digital Twin state.
POST/state/actions/{actionKey}: Triggers the specified action (e.g., /state/actions/switch_on) in the Digital Twin state. The raw body contains the action request payload.
GET/state/relationships: Retrieves the list of relationships in the Digital Twin state.
GET/state/relationships/{relationshipName}/instances: Retrieves the instances of the specified relationship (e.g., /state/relationships/insideIn/instances) in the Digital Twin state.
GET/storage: Retrieves Storage Statistics from the target Digital Twin
POST/storage/query: Allows the execution of a query, where the query structure is specified through a JSON Message in the request Body. For additional information about the Query System see Query System Page
Note: Replace {propertyKey}, {actionKey}, and {relationshipName} with the actual values you want to retrieve or trigger.
+Make sure to use the appropriate HTTP method (GET, POST) and include any required parameters or payload as described in each endpoint’s description. For more detailed information, refer to the Postman Collection for this API available in the folder api: http_adapter_api_postman.json
Example of Storage Query Requests are the following:
Retrieve the first 4 Digital Twin State Variations
