Client Side Measure
Not all measures can be executed on server side. This is the case for example for direct measures which have to collect directly some data in physical world. To address this, the MEASURE Platform provide an Agent, deployed on client side which allows to execute standard measure on client.
- Download the last packaging of the Agent: https://github.com/ITEA3-Measure/MeasureAgent/releases
- On your client, unzip the agent and configure it by feeling the application.properties file.
Configure the Agent
| Property | Description |
|---|---|
| measure.repository.path | Path of local directory containing measures |
| measure.server.adress | Ip of MeasurePlatform Server |
| measure.agent.name | Name of the Agent (Must be Unique) |
Example :
measure.repository.path=/home/measure/storage
measure.server.adress=xxx.xxx.xxx.xxx/measure
measure.agent.name= MyAgent
You can also build the agent directly from GitHub sources with Maven.
> mkdir ./measure-agent
> cd ./measure-agent
> git clone https://github.com/ITEA3-Measure/MeasureAgent.git
> mvn package
During the comfiguration, you have define the path of the storage folder, a directory which will contain the measures deployed on your agent.
To deploy a measure :
- Unzip the packaged Measure
- Copy the unziped Measure on storage folder.
Expected Directory Organisation Example:
/agent/storage
/agent/storage/RandomGenerator
/agent/storage/RandomGenerator/RandomGenerator-1.0.0.jar
/agent/storage/RandomGenerator/MeasureMetadata.xml
java -jar measure-agent-1.0.0.jar
Visualise Agent on Server Side
When an agent is started, it is automaticaly registred on the Measure Platform. The list of agents actually registered on the Measure Platform can be consulted on the "Platform > Remote Agent" page.
Visualise Available Measure
The measures deploy on agents can be visualise on the Measure Catalogue page like others measures deploy on server. The Host indicate the name of the agent which provide this measure.
Instantiate Client Side Measure
Similar server side measures, you have to create an instance of a client side measure in order to collect it.
The only differences to a server-side measure is that, at this time it is not possible to execute once a client-side measure. The client-side measure instance has to be scheduled.