Search

Help

Page 1 of 4. Showing 34 results (0.005 seconds)

  1. IoT Data Processing agent Deployment

    https://linksmart.eu/redmine/linksmartopensource/linksmartservices/dataprocessingagent.git > mvn install Check out the IoT Agents sources from GPL GIT repository … " "https://linksmart.eu/repo/service/local/artifact/maven/redirect?r=releases&g=eu.linksmart.services.events.&a=iot.learning.impl&c=all&v=LATEST" IoT Learning Agent (MQTT) (GPL) > wget q O "agent.jar
    LinkSmart® IoT AgentsJul 24, 2017
  2. IoT agents configuration

    Applications: IoT DataProcessing, Learning agents (REST and MQTT) Configures: DataProcessing Core, CEML, GC Utils, Springboot, Log4j File: conf.cfg To the default configuration of the agents or agents component an configuration file must be given. The configuration file will be searched in following location
    LinkSmart® IoT AgentsJul 24, 2017
  3. IoT Agents (Under construction)

    The site is currently under construction Summary The IoT agents where developed for all kind of storeless data processing, from simple data annotation or aggregation to complex data machine learning techniques. The agents are ideal for intelligent onDemand data management or analysis in IoT environments, from edge
    LinkSmart® IoT AgentsJul 25, 2017
  4. IoT Agent Architecture

    asynchronous messages to which the IoT Learning Agent (LA) or LAs are subscribed. On the other hand, the Models subscribe to the data, provided by the clients … are established using Paho clients. While the logical connections between the components and the Broker/s is managed by StaticBroker. This means, there are as many
    LinkSmart® IoT AgentsJul 24, 2017
  5. IoT Data-Processing Agent API

    file (see ). File based API The file base API or BootstrappingFeeder was developed to allow having preloaded events and statements on the agent. For deploy … ! MQTT API The agent it always listening a topic for new statement (see ) in an incoming "control" broker, by default the is "statement/add" and "tcp://localhost
    LinkSmart® IoT AgentsJul 24, 2017
  6. IoT Data-Processing Agent Results

    using 1 core as base, while DFM used 2 cores as base. Interpretation The test was performed until one of the three sides reached its limit. In this test … over the load used in this experiment. Scalability perspective The test shows that the effects of a heavy load in the system affect different on other components
    LinkSmart® IoT AgentsJul 24, 2017
  7. Component Diagrams

    LinkSmart® LocalConnectJul 11, 2017
  8. IoT Agents Use Cases

    the Agent execution environment. Operation Type Type of the request. Create Creates one statement and exist so lo the request finished or is deleted. Update … to be persisted. The stream is stored in some persistent system. Extern All request that produces any side effect outside the Agent execution environment. These use
    LinkSmart® IoT AgentsJul 24, 2017
  9. IoT Data-Processing agent Statement

    The DP Statement payload This type of events encapsulate a DP statement used to deploy the query statement on agent. It contains 10 properties of which only 2 … on the API is being used. The ID is unique identifier in an agent. If the the ID is not provided, then is generated by hashing (SHA256) the Statement value, this means
    LinkSmart® IoT AgentsJul 24, 2017
  10. Device Gateway

    execution: task, timer and service. task execution means the Device Agent is executed only once per request coming from Services component. The last value is cached … /resources configured to use MQTT protocol. This component passes data from POST/PUT/DELETE HTTP requests to the corresponding Device Agents by writing
    LinkSmart® LocalConnectJul 11, 2017