RifidiWiki - User contributions [en]

Edge Server Configuration

2012-01-11T13:55:27Z

MacyWales:

This page explains the various configuration options of the Rifidi Edge Server
=RifidiEdgeServer.ini=
The RifidiEdgeServer.ini is a property file that contains options for various options when the edge server starts up.
==rifidiserver.ini file==
As of release 1.2.0, the default rifidiserver.ini file looks [http://www.andrewflusche.com/services/virginia-reckless-driving-ticket-defense/Virginia reckless driving] like this:
<pre>
-os
${target.os}
-ws
${target.ws}
-arch
${target.arch}
-nl
${target.nl}
-vmargs
-Declipse.ignoreApp=true
-Dosgi.console
-Dosgi.noShutdown=true
-Dorg.rifidi.edge.configuration=config/rifidi.xml
-Dosgi.clean=true
-Dorg.osgi.framework.bootdelegation=javax.xml.ws
-Dcom.sun.management.jmxremote.port=2021
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=127.0.0.1
-Dorg.rifidi.edge.core.rmi.port=1101
-Dorg.rifidi.edge.ale.port=8081
-Dorg.rifidi.edge.ale.host=127.0.0.1
-Dosgi.framework.extensions=org.eclipse.equinox.weaving.hook
-Dorg.aspectj.osgi.verbose=true
-Dorg.rifidi.edge.autostart=true
-Dorg.rifidi.edge.logging=config/logging.properties
-Dorg.rifidi.ui.notify=true
</pre>

==Console==
;-console
:This starts up the OSGi console so that you can interact with the edge server from the command line. For a list of commands that are available see [[Edge Server Commands]]. If you would like the console to be available over the network, supply a port after the -console (e.g. -console 2020). Now it is possible to telnet into the server at the given port. It is recommended that you [http://www.phuketproperty.com/Phuket property] use ssh tunneling for security reasons (i.e. first ssh to the machine that is running the edge server, then telnet to the console). One [http://www.performer5pills.info/ performer5] thing to note is that after you telnet to the OSGi console, you cannot use [http://vihan.vn thiet ke web] the <tt>exit</tt> command as you normally would to [http://maleextrareviews.info/ maleextra] close the telnet session. This is because <tt>exit</tt> will be caught by the OSGi console and will perform a System.exit(). Instead, to exit the telnet session [http://www.shoppharmacycounter.com/t-dietpillsonline.aspxdiet pills] while keeping the server running, just close the telnet window.

==VMArgs==
VMArgs must follow the <tt>-vmargs</tt> flag in the .ini file. They must [http://www.instantperformeroil.info/ instant performer] start with <tt>-D</tt>. Default values can be found in the <tt>bundle.properties</tt> file in the spring directory for the appropriate [http://www.shoppharmacycounter.com/t-phentermine.aspx phentermine] option. Important VM args:
;-Dorg.rifidi.edge.configuration
:This is the path to the persistence file. See [[#rifidi.xml]].
;-Dcom.sun.management.jmxremote.port
:The port to open up JMX on. This is important if you are using a program like VisualVM to profile the server
;-Djava.rmi.server.hostname
:The hostname to open up the RMI registry at. Default is <tt>127.0.0.1</tt>
;-Dorg.rifidi.edge.core.rmi.port
:The port of the RMI registry Default is <tt>1101</tt>
;-Dorg.rifidi.edge.ale.host
:The hostname to publish the ALE webservices at. Default is <tt>127.0.0.1</tt>
;-Dorg.rifidi.edge.ale.port
:The port to publish the ALE webservices at. Default is <tt>8081</tt>
;-Dorg.rifidi.edge.ale.read
:The service name of the ALE reading service. Default is <tt>ALEService</tt>
;-Dorg.rifidi.edge.ale.logicalreader
:The service name of the ALE logical reader service. Default is <tt>ALELRService</tt>
;-Dorg.rifidi.home
:The Rifidi directory. If not set, it defaults to ${user.dir}
;-Dorg.rifidi.ui.notify
:If set to true, reader adapters will send tag notifications to workbench. Default is true

=rifidi.xml=
The rifidi.xml file is the persistence file for the Rifidi Edge Server. The two important services that are saved are Reader Configurations and Command Configurations.

==Loading a configuration file==
Whenever the edge server starts up, it looks for the file that is specified in the <tt>org.rifidi.configuration</tt> vm flag. After the configuration file is read, the server will attempt to recreate all [http://www.smartpixels.net/ seo India] services specified in the file. If a needed factory is not available, the service will be skipped and [http://www.seoagency.com.vn/seo.php dich vu seo] recreated when the factory [http://www.eyesecretsreview.info/ eye secrets] becomes available. For example, suppose the configuration file has an Alien Reader Configuration and an [http://www.seoagency.com.vn cong ty seo] LLRP Reader Configuration. Suppose that when the server starts up, only the Alien plugin is available (so the Alien Reader Factory is [http://buybreastenlargement.com/ breast enlargements] available, but the LLRP Reader [http://www.intivarreview.info/ intivar]Factory is not). At this point the Alien [http://www.herbalweightlossaid.com/ slimming pills] Reader is recreated. If later the LLRP plugin is installed, then the LLRP reader will be recreated.

==File Structure==
The edge server uses JAXB to persist a configuration file [http://www.supplementstoweightloss.com/t-dietpills.aspx diet pills]. Each service will have a serviceID and a factoryID. The serviceID is the unique name of the service, and is used when using the [http://buysexualenhancers.com/ sexual enhancers] service (such as starting a session on a reader). The factoryID is the ID of the factory that can create a service. The following is an example of file that [http://www.supplementstoweightloss.com/t-dietpills.aspx diet supplements] has one Alien Reader saved.
<pre>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configurationStore>
<services>
<attributes>
<entry>
<key>ReconnectionInterval</key>
<value>500</value>
</entry>
<entry>
<key>Port</key>
<value>20000</value>
</entry>
<entry>
<key>InvertExternalOutput</key>
<value>0</value>
</entry>
<entry>
<key>PersistTime</key>
<value>-1</value>
</entry>
<entry>
<key>Username</key>
<value>alien</value>
</entry>
<entry>
<key>Password</key>
<value>password</value>
</entry>
<entry>
<key>InvertExternalInput</key>
<value>0</value>
</entry>
<entry>
<key>ReaderNumber</key>
<value>0</value>
</entry>
<entry>
<key>ExternalOutput</key>
<value>0</value>
</entry>
<entry>
<key>IpAddress</key>
<value>127.0.0.1</value>
</entry>
<entry>
<key>MaxNumConnectionAttempts</key>
<value>10</value>
</entry>
<entry>
<key>RFAttenuation</key>
<value>0</value>
</entry>
</attributes>
<factoryID>Alien</factoryID>
<serviceID>Alien_1</serviceID>
</services>
</configurationStore>
</pre>

Edge Server Getting Started

2011-12-20T04:02:55Z

MacyWales:

Thank you for your interest in the Rifidi Edge Server -- an open source platform for developing and deploying RFID applications. Here's how [http://www.culinarydepotinc.comrestaurant supply] to get started:

==Run it==
# '''Download''' the [http://sourceforge.net/projects/rifidi/ Edge Server] from our sourceforge page. The download comes bundled with two programs: the '''Edge Server''' which does the core work of connecting to sensors (such as RFID readers), collecting tag information, and making that data available. It ships with adapters for Alien, LLRP, Awid, and several other types of RFID readers. It also [http://www.herbalweightlossaid.com/ slimming pills] ships with ALE support. The second program is '''Workbench''' which is a user interface that allows you to control the edge server and view tag information that it is collecting, as well as experiment with ALE.
# '''Download''' [http://sourceforge.net/projects/rifidi/files/ Rifidi Emulator]. This program allows you to [http://maleextrareviews.info/ maleextra] virtualize several popular types of RFID readers on your desktop.
# '''Follow''' the [[Workbench User's Guide|quick start guide]] to start getting tag reads back from virtual readers.

==Develop Your Own Application==
The edge server by itself allows you to connect to [http://www.smartpixels.net/ seo India] sensors and collect tag data from them, but if you really want to put it to work, you will need to develop your own applications that run on the edge server.
# '''Download''' our SDK (Standard Development Kit). This provides our API, sourcecode and [http://www.intivarreview.info/ intivar] examples to help you get started. You can find out how to set up a development [http://www.eyesecretsreview.info/ eye secrets] environment here: [[Edge Server Development Environment]].
# '''Develop''' an application. There are several example [http://buysexualenhancers.com/ sexual enhancers] applications which ship with the Rifidi Edge Server. You can read about them in detail in the [http://www.performer5pills.info/ performer5] developer guide that is included in the release
# [[How_to_export_your_custom_Rifidi_application|'''Export''']] your application
# '''Deploy''' the application you've built. Once you've built and tested your [http://buybreastenlargement.com/ breast enlargements] application, you can deploy it onto the edge [http://www.shoppharmacycounter.com/t-dietpillsonline.aspx diet supplements] server that you've downloaded.

==Contribute Back==
The Rifidi Edge Server is open source. This means that if you find bugs or have ideas for useful features, you have the ability to extend the edge server yourself! We will gladly welcome [http://www.instantperformeroil.info/ instant performer] contributions of any sort (code, documentation, testing, etc) and encourage you to submit these back. To get involved with the community:
# '''Visit''' our [http://forums.rifidi.org forums]. This is the best place to talk to our developers and users of Rifidi.
# '''Submit''' feature requests and bug reports. We have a [https://trac.rifidi.org bug tracking system] that manages outstanding feature requests and bugs. Before you submit bug reports here [http://www.supplementstoweightloss.com/ best weight loss], we ask that you visit us on the forums first and make sure that there isn't a known solution for your question already
# '''Contribute''' to our wiki. We gladly welcome any documentation in the form of HOWTOs, example code, tutorials, or any other form that you find helpful.

Rifidi Edge Server Application Tutorials

2011-12-14T10:26:43Z

MacyWales:

With release 1.2.0 of the Rifidi Edge Server, a [http://tfssolar.com/7228/global-community-communications-alliance-solar-array/global community communications alliance] developer API is provided to [http://www.andrewflusche.com/services/virginia-reckless-driving-ticket-defense/Virginia reckless driving] make writing Rifidi Applications much easier. The best place to find out how to write applications is the developer [http://www.diamondlinks.net/link building] document that is [http://en.wikipedia.org/wiki/Bankers_Life_and_Casualtybankers life] released as part of the SDK [http://www.proposable.com proposal software] release. There are several example applications [http://thepartyhub.com/contact-us/ party places] included with the SDK and the developer documentation describes them in detail [http://www.internetreputationmanagement.com reputation management online].
[http://www.bestpills4weightloss.com/weight loss pills]

*[http://rifidi.org/guides/Rifidi_Edge_Server_Developer_1.2.pdf Developer's Guide for 1.2.0]

Rifidi Edge Server Application Tutorials

2011-11-29T08:52:53Z

MacyWales:

With release 1.2.0 of the Rifidi Edge Server, a [http://tfssolar.com/7228/global-community-communications-alliance-solar-array/global community communications alliance] developer API is provided to [http://www.andrewflusche.com/services/virginia-reckless-driving-ticket-defense/Virginia reckless driving] make writing Rifidi Applications much easier. The best place to find out how to write applications is the developer [http://www.diamondlinks.net/link building] document that is [http://en.wikipedia.org/wiki/Bankers_Life_and_Casualtybankers life] released as part of the SDK [http://www.proposable.com proposal software] release. There are several example applications [http://thepartyhub.com/contact-us/ party places] included with the SDK and the developer documentation describes them in detail [http://www.internetreputationmanagement.com reputation management online].

*[http://rifidi.org/guides/Rifidi_Edge_Server_Developer_1.2.pdf Developer's Guide for 1.2.0]

Rifidi Edge Server Application Tutorials

2011-11-09T10:29:42Z

MacyWales:

With release 1.2.0 of the Rifidi Edge Server, a developer API is provided to [http://www.andrewflusche.com/services/virginia-reckless-driving-ticket-defense/Virginia reckless driving] make writing Rifidi Applications much easier. The best place to find out how to write applications is the developer [http://www.diamondlinks.net/link building] document that is released as part of the SDK [http://www.proposable.com proposal software] release. There are several example applications [http://thepartyhub.com/contact-us/ party places] included with the SDK and the developer documentation describes them in detail [http://www.internetreputationmanagement.com reputation management online].

*[http://rifidi.org/guides/Rifidi_Edge_Server_Developer_1.2.pdf Developer's Guide for 1.2.0]

Rifidi roadmap

2011-10-28T02:23:55Z

MacyWales:

This page discusses some long range plans for the Rifidi project.

=Current State=

Currently, the Rifidi products (Tag Streamer, and Emulator) are two [http://www.bankerslifeinsurance.com/bankers life] totally separate [http://www.skin-products-review.com/breastactives breast actives] [http://itshumour.blogspot.com/2009/07/funny-nursery-rhymes-remixed.html nursery rhymes] [http://www.celebrationswineclub.com/ Wine Clubs] [http://itshumour.blogspot.com/2009/05/crazy-artistic-tattoos.html crazy tattoos][http://dentaldentistsolutions.blogspot.com/2009/10/process-and-pictures-dental-implants.html dental implants][http://itshumour.blogspot.com/2009/09/top-10-hilarious-quotes.html hilarious quotes][http://itshumour.blogspot.com/2010/06/twenty-hilarious-funny-quotes.html funny quotes][http://itshumour.blogspot.com/2011/07/funny-marriage-jokes.html funny jokes][http://itshumour.blogspot.com/2011/08/funny-statuses-quotes-for-facebook.html funny status for facebook] being developed with [http://www.chetankapur.com/ Chetan Kapur] [http://alliancetransport.com.sgbus rental] the service-oriented [http://www.andrewflusche.com/services/spotsylvania-dui-lawyer/Spotsylvania DUI lawyer] paradigm that osgi provides. this causes several problems:

*Two Separte Development Cycles for Rifidi Tag Streamer, and Emulator
** Version Numbers apply only to releases, not to underlying services provided by osgi plugins
** too much code is copied and not shared
*There is alot of functionality that is not [http://www.arcat.com/arcatcos/cos44/arc44722.html rhino deck] separated into plugins
**Stable code mixed with development code
**If only one small part of a class changes, the whole plugin has to be updated
*Rifidi is missing an eclipse-like 'update' functionality

As a result, we end up with two separate, but related [http://www.hmcdisplay.com/staging.html Portable Stage] projects that are loosely-coupled

=Solution through Service Oriented Architecture=

In order to tie the services-oriented design that osgi allows for. We can achieve this by following the following best practices:

* Functionality needs to be separated into [http://www.cloutshoppe.comonline shop singapore] services (i.e. plugins).
* osgi plugins should be versioned separately from releases. We can do this in the manifest file of the plugin
* Each bundle should have a maintainer. This can also be specified in the [http://www.bestpills4weightloss.com/ best weight loss pills] plugin's manifest [http://www.miiny.comdeals singapore].
* The most important idea is that Rifidi should be treated as '''one''' application with several possible ways of assembling functionality.

=Rifidi As Single Application=
If Rifidi is a single application, it gives several benefits:
*'''Single Installer''' - There can be a single, small Rifidi Installer that allows [http://www.bowtrolcoloncleanseblog.com bowtrol] users to install the Rifidi functionality that they want. For example, once they have the base application running, they can choose to install the 'emulator' packages or the 'tag streamer' packages.
*'''Update Functionality''' - When a user wants the latest version of the code, he can update the application, which will install only the latest osgi plugins instead of having [http://www.zetaclearspot.com zetaclear] to download the whole rifidi application again.
*'''Reliability''' - By focusing on the functionality at the [http://www.zetaclearspot.com zetaclear] package level, we can note when a package changes and update the version number of the package itself. In addition, plugin dependencies can specify version number that they depend on. This allows us to know [http://featherranch.com/ dog training] which package versions work with the current code ==Related Links==

[http://www.cellulite.co.uk/ '''cellulite'''] in case something breaks. Because each plugin can be tagged in the SVN, a 'release' is simply a collection of plugin version numbers.
*'''User Upgrade Path''' - By having an installer with the ability to add new[http://www.busbooking.sgbus service] [http://dentaldentistsolutions.blogspot.com/2009/10/process-and-pictures-dental-implants.html dental implants][http://itshumour.blogspot.com/2009/09/top-10-hilarious-quotes.html hilarious quotes][http://itshumour.blogspot.com/2010/06/twenty-hilarious-funny-quotes.html funny quotes][http://itshumour.blogspot.com/2011/07/funny-marriage-jokes.html funny jokes][http://itshumour.blogspot.com/2011/08/funny-statuses-quotes-for-facebook.html funny status for facebook] [http://www.propertyprice.com.sg/Property Prices]Rifidi Products, for example:

[[Image:RifidiRoadmap.png]]

=Steps to Complete=
# Separate functionality into plugins and identify common code that is currently being duplicated.

# Design new packages for the duplicated code. The new packages should be able to be used by all [http://startutor.sgtuition centre] products.
# Develop a 'best practices' guide for how to number osgi packages. Go through all packages and give them version numbers
# Create a new svn repository and add all new packages to it [http://www.streetdeal.sghotel deals]
# Add update functionality within the products
# Host site for serving package updates
# Develop common UI framework

Rifidi roadmap

2011-10-13T05:17:03Z

MacyWales:

This page discusses some long range plans for the Rifidi project.

=Current State=

Currently, the Rifidi products (Tag Streamer, and Emulator) are two [http://www.bankerslifeinsurance.com/bankers life] totally separate [http://www.skin-products-review.com/breastactives breast actives] [http://itshumour.blogspot.com/2009/07/funny-nursery-rhymes-remixed.html nursery rhymes] [http://www.celebrationswineclub.com/ Wine Clubs] [http://itshumour.blogspot.com/2009/05/crazy-artistic-tattoos.html crazy tattoos][http://dentaldentistsolutions.blogspot.com/2009/10/process-and-pictures-dental-implants.html dental implants][http://itshumour.blogspot.com/2009/09/top-10-hilarious-quotes.html hilarious quotes][http://itshumour.blogspot.com/2010/06/twenty-hilarious-funny-quotes.html funny quotes][http://itshumour.blogspot.com/2011/07/funny-marriage-jokes.html funny jokes][http://itshumour.blogspot.com/2011/08/funny-statuses-quotes-for-facebook.html funny status for facebook] being developed with [http://www.chetankapur.com/ Chetan Kapur] the service-oriented paradigm that osgi provides. this causes several problems:

*Two Separte Development Cycles for Rifidi Tag Streamer, and Emulator
** Version Numbers apply only to releases, not to underlying services provided by osgi plugins
** too much code is copied and not shared
*There is alot of functionality that is not separated into plugins
**Stable code mixed with development code
**If only one small part of a class changes, the whole plugin has to be updated
*Rifidi is missing an eclipse-like 'update' functionality

As a result, we end up with two separate, but related projects that are loosely-coupled

=Solution through Service Oriented Architecture=

In order to tie the services-oriented design that osgi allows for. We can achieve this by following the following best practices:

* Functionality needs to be separated into services (i.e. plugins).
* osgi plugins should be versioned separately from releases. We can do this in the manifest file of the plugin
* Each bundle should have a maintainer. This can also be specified in the plugin's manifest.
* The most important idea is that Rifidi should be treated as '''one''' application with several possible ways of assembling functionality.
=Rifidi As Single Application=
If Rifidi is a single application, it gives several benefits:
*'''Single Installer''' - There can be a single, small Rifidi Installer that allows [http://www.bowtrolcoloncleanseblog.com bowtrol] users to install the Rifidi functionality that they want. For example, once they have the base application running, they can choose to install the 'emulator' packages or the 'tag streamer' packages.
*'''Update Functionality''' - When a user wants the latest version of the code, he can update the application, which will install only the latest osgi plugins instead of having [http://www.zetaclearspot.com zetaclear] to download the whole rifidi application again.
*'''Reliability''' - By focusing on the functionality at the [http://www.zetaclearspot.com zetaclear] package level, we can note when a package changes and update the version number of the package itself. In addition, plugin dependencies can specify version number that they depend on. This allows us to know which package versions work with the current code ==Related Links==

[http://www.cellulite.co.uk/ '''cellulite'''] in case something breaks. Because each plugin can be tagged in the SVN, a 'release' is simply a collection of plugin version numbers.
*'''User Upgrade Path''' - By having an installer with the ability to add new [http://dentaldentistsolutions.blogspot.com/2009/10/process-and-pictures-dental-implants.html dental implants][http://itshumour.blogspot.com/2009/09/top-10-hilarious-quotes.html hilarious quotes][http://itshumour.blogspot.com/2010/06/twenty-hilarious-funny-quotes.html funny quotes][http://itshumour.blogspot.com/2011/07/funny-marriage-jokes.html funny jokes][http://itshumour.blogspot.com/2011/08/funny-statuses-quotes-for-facebook.html funny status for facebook] Rifidi Products, for example:

[[Image:RifidiRoadmap.png]]

=Steps to Complete=
# Separate functionality into plugins and identify common code that is currently being duplicated.

# Design new packages for the duplicated code. The new packages should be able to be used by all products
.
# Develop a 'best practices' guide for how to number osgi packages. Go through all packages and give them version numbers
# Create a new svn repository and add all new packages to it[http://www.amaliadraghici.ro/portofolio/Machiaj%20mireasa/list/1 machiaj mireasa]
# Add update functionality within the products
# Host site for serving package updates
# Develop common UI framework