sensorweaver:admin-guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sensorweaver:admin-guide [2015-11-10 16:54] – [Bundles configuration] luigi.fortunati | sensorweaver:admin-guide [2017-12-04 14:40] (current) – davide | ||
|---|---|---|---|
| Line 20: | Line 20: | ||
| We strongly recommend Apache Karaf as the OSGi container of choice. You have two choices: | We strongly recommend Apache Karaf as the OSGi container of choice. You have two choices: | ||
| - | * Download a preconfigure Apache Karaf bundle | + | * <del>Download a preconfigure Apache Karaf bundle</ |
| * Download Apache Karaf and use [[http:// | * Download Apache Karaf and use [[http:// | ||
| === SensorWeaver Karaf Bundle === | === SensorWeaver Karaf Bundle === | ||
| - | The preconfigured SensorWeaver karaf bundle can be downloaded from this {{: | + | <del>The preconfigured SensorWeaver karaf bundle can be downloaded from this {{: |
| That is based on Karaf 3.0.2 and already includes a default configuration that will launch the execution environment (Middleware included) with minimal effort required. | That is based on Karaf 3.0.2 and already includes a default configuration that will launch the execution environment (Middleware included) with minimal effort required. | ||
| - | You can install your bundles in the container and test it using Karaf [[http:// | + | You can install your bundles in the container and test it using Karaf [[http:// |
| === SensorWeaver features === | === SensorWeaver features === | ||
| Line 33: | Line 33: | ||
| Alternatively you can download an Apache Karaf Distribution from the [[http:// | Alternatively you can download an Apache Karaf Distribution from the [[http:// | ||
| - | Please refer to Karaf [[http:// | + | Please refer to Karaf [[http:// |
| + | |||
| + | To use sensorweaver features you first have to setup the maven repo in file ' | ||
| + | |||
| + | The last lines of the file should look like this: | ||
| + | <file properties org.ops4j.pax.url.mvn.cfg> | ||
| + | .... | ||
| + | http://repository.springsource.com/ | ||
| + | http:// | ||
| + | http:// | ||
| + | </ | ||
| + | |||
| + | Including the snapshot repository is not mandatory. | ||
| + | |||
| + | To install the whole set of middleware bundles, start karaf and execute the following karaf console commands: | ||
| + | |||
| + | <code console> | ||
| + | karaf@root()> | ||
| + | Adding feature url mvn: | ||
| + | karaf@root()> | ||
| + | karaf@root()> | ||
| + | START LEVEL 100 , List Threshold: 50 | ||
| + | ID | State | Lvl | Version | Name | ||
| + | ------------------------------------------------------------------- | ||
| + | 52 | Active | 80 | 2.3.1 | Gson | ||
| + | 53 | Active | 80 | 18.0.0 | ||
| + | 54 | Active | 80 | 2.0.6 | Messaging Service API | ||
| + | 55 | Active | 90 | 2.0.7 | MQTT Messaging Service | ||
| + | 56 | Active | 80 | 2.1.2 | Middleware API | ||
| + | 57 | Active | 90 | 2.1.2 | Middleware Service implementation | ||
| + | 58 | Active | 80 | 2.5 | Commons Lang | ||
| + | 69 | Active | 80 | 1.0.2 | Paho MQTT Client | ||
| + | </ | ||
| + | |||
| + | The feature will install with default bundle configuration. At this point you can stop karaf and manually configure the bundles by modifying property files under the karaf ' | ||
| ==== Bundles configuration ==== | ==== Bundles configuration ==== | ||
| Line 63: | Line 97: | ||
| </ | </ | ||
| - | Messaging layer can follow one of these broker authentication mechanisms: | + | Messaging layer can follow one of these broker authentication mechanisms |
| - | * anonymous: broker must be set to allow anonmyous clients | + | * //anonymous//: broker must be set to allow anonmyous clients |
| - | * password: username/ | + | * //password//: by setting the mode to password the messaging layer will connect to the broker using the //username// and //password// provided in the available fields. Refer to the broker |
| - | * certificate: | + | * //certificate//: certificate based authentication. Refer to [[https:// |
| Middleware configuration includes a scope name assigned to the middleware instance. A scope identify an area of visibility of data on the Middleware. | Middleware configuration includes a scope name assigned to the middleware instance. A scope identify an area of visibility of data on the Middleware. | ||
| Line 76: | Line 110: | ||
| nodeId= | nodeId= | ||
| </ | </ | ||
| + | |||
| + | The scope defines a domain under which messages are published on the broker and is the first level of each topic used for message publication. | ||
| + | The nodeId, if not provided, defaults to the client hostname. It can be set manually by configuration. | ||
sensorweaver/admin-guide.1447174478.txt.gz · Last modified: 2015-11-10 16:54 by luigi.fortunati