RifidiWiki - User contributions [en]

Edge Server Configuration

2011-11-01T04:57:32Z

Seoagent: /* Loading a configuration file */

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 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 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 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 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 start with <tt>-D</tt>. Default values can be found in the <tt>bundle.properties</tt> file in the spring directory for the appropriate 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 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 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 available, but the LLRP Reader Factory is not). At this point the Alien 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 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 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 Configuration

2011-11-01T04:57:16Z

Seoagent: /* Loading a configuration file */

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 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 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 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 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 start with <tt>-D</tt>. Default values can be found in the <tt>bundle.properties</tt> file in the spring directory for the appropriate 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 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 becomes available. For example, suppose the configuration file has an Alien Reader Configuration and an LLRP Reader Configuration. Suppose that when the server starts up, only the Alien plugin is available (so the Alien Reader Factory is available, but the LLRP Reader Factory is not). At this point the Alien 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 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 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 Configuration

2011-11-01T04:56:58Z

Seoagent: /* Console */

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 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 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 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 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 start with <tt>-D</tt>. Default values can be found in the <tt>bundle.properties</tt> file in the spring directory for the appropriate 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 services specified in the file. If a needed factory is not available, the service will be skipped and recreated when the factory becomes available. For example, suppose the configuration file has an Alien Reader Configuration and an LLRP Reader Configuration. Suppose that when the server starts up, only the Alien plugin is available (so the Alien Reader Factory is available, but the LLRP Reader Factory is not). At this point the Alien 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 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 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>

Rifidi Edge Server Application Tutorials

2011-11-01T04:55:59Z

Seoagent:

With release 1.2.0 of the Rifidi Edge Server, a developer API is provided to make writing Rifidi Applications much easier. The best place to find out how to write applications is the developer 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]

Edge Server Architecture

2011-11-01T04:55:02Z

Seoagent: /* OSGi */

This page describes several aspects of the Rifidi Edge Server Core. It is intended for developers to understand how the core is structured.
=Overview=
There are two main aspects to understanding the edge server. The first is the three architectural layers that facilitate the flow of data from sensor to a designated endpoint. The second is the runtime and how it uses service oriented architecture and OSGi to be dynamic and light weight.
==Layers==
This section shows the three conceptual architectural layers that data passes through on its journey from sensors to whatever endpoint the user chooses.

[[Image:Dataflow3.png|thumbnail|400px|Dataflow through the three Architectural layers in the Rifidi Edge Server]]

===Sensor Abstraction Layer===
The purpose of the edge server is to connect to any kind of sensors (e.g. RFID readers, Barcode readers, Mobile Devices) and collect information from them. In many scenarios, this consists of connecting to a Gen2 fixed reader (such as Alien 9800, Motorolla LLRP, etc), and collecting EPC information. However, the edge server is designed in a way so that the edge server to collect many kinds of data (active, passive, etc) from many kinds of devices. This layer allows users to connect to devices in a sensor-agnostic way to collect the kind of data required for the application.

===Application Engine Layer===
For most applications it is not desirable to save every event that the sensors produce. Many sensors can send 1,000 of events a second, a large number of which might be duplicates. Most applications are interested in events that are one-level higher than the raw events produced by sensors. For examples, an ERP system is probably interested in the event of a box arriving in area 1, and it is not desirable for the ERP system to do the work of filtering and processing all of duplicate reads the sensor produces.

Complex Event Processing (CEP) is a paradigm of viewing data as ephemeral events (an event stream) and identifying meaningful (i.e. business) events from the stream using rules. Rifidi Edge Server uses a Complex Event Processor called Esper. It allows you to write queries using an SQL-like syntax:
<pre>
select * from ReadCycle where ReaderID='gate_1'
</pre>

One of the most important aspects of CEP is being able to use incorporate temporal knowledge into the queries. This allows you to phrase queries like "Send an order_complete event when an itemA event is followed by an itemb event" or "send an order_cancelled event when an itemb event is not seen within 10 min of a itemA event."

The Application Engine Layer is intended to let application developers build much of the functionality of their RFID applications using esper queries.

===Communication Layer===
After data has been processed, it probably needs to be handed up to some kind of application-dependent system. For example, some users might want the data to be stored in an [http://physioactive.sg/ massage therapy singapore] database, others might want it to be pushed into an ERP system like SAP or handed to a [http://www.inleds.com/products/?cid=2 led downlight singapore] Rich User Interface of some sort. The edge server has several built in connectors to use, namely JMS and Web Services (via Spring's remoting framework). However, as this is application dependant, it is possible to write your own connector (such as a TCP/IP socket connection) if the application needs it.

In addition, the edge server also provides a [http://www.inleds.com/ singapore led lighting] built-in web container and MVC framework so that web applications can be deployed directly.

==OSGi==
OSGi is a dynamic modules system for Java. It provides several pieces of functionality including the following:
# A deployment unit (called a bundle), which is a [http://www.premier-football.net soccer jersey store] normal JAR with some extra information in the Manifest.
# A lightweight runtime that allows bundle lifecycle to be controlled. In other words, you can start, stop, and update bundles at [http://thepartyhub.com/Showcase party artists] runtime.
# Dependencies are explicitly stated in the Manifest either as "bundle dependencies" or "package dependencies".
# Classes are only visible to other bundles if their containing packages have been exposed. This allows developers to hide classes that should be strictly internal.
# The runtime provides a [http://thepartyhub.com/ event planners singapore] service registry -- a system-wide repository for bundles to provide functionality.

The edge server is simply a collection of bundles that run in an OSGi environment (Equinox). Functionality between bundles is shared by means of services that are available in the service registry. Because bundles can be started and stopped while the rest of the server is still running, we can update non-essential parts of the edge server without restarting it.

=Services=
In the Edge Server, services are POJOs that provide a specific piece of functionality to other components and are registered in the OSGi Registry. For more information see [[How to use OSGi Services]]
== Core Services==
The following services are provided by the core bundle.
===Reader Data Access Object===
'''Purpose''': Provide access to sensor configurations that have been created. 
'''Interface''': <tt>org.rifidi.edge.core.daos.ReaderDAO</tt> 
'''Methods''' 
* <tt>Set<AbstractSensor> getReaders()</tt> Get all available sensor configurations
* <tt>AbstractSensor getReaderByID(String ID)</tt> - Get the sensor with the supplied ID
* <tt>Set<AbstractSensorFactory> getReaderFactories()</tt> - Get all registered sensor factories
* <tt>AbstractSensorFactory getReaderFactoryByID()</tt> - Get the sensor factory with the supplied ID
===Command Data Access Object===
'''Purpose''': Provide access to command configurations that have been created. 
'''Interface''': <tt>org.rifidi.edge.core.daos.CommandDAO</tt> 
'''Methods''' 
* <tt>Set<AbstractCommandConfiguration> getCommands()</tt> Get all available command configurations
* <tt>AbstractCommandConfiguration getCommandByID(String ID)</tt> - Get the command configuration with the supplied ID
* <tt>Set<AbstractCommandConfigurationFactory> getCommandFactories()</tt> - Get all registered command configuration factories
* <tt>AbstractCommandConfigurationFactory getCommandFactoryByID(String ID)</tt> - Get the command configuration factory with the supplied ID
* <tt>AbstractCommandConfigurationFactory getCommandFactoryByReaderID(String ID)</tt> - Get the command configuration factory with the supplied sensor ID

===Configuration Service===
'''Purpose''': Provide a way to save and load configurations from persistence. Configurations (such as Sensor Configurations or Command Configurations) are created using a factory (that must be registered). Configurations have Attributes which can be changed via getters and setters. 
'''Interface''': <tt>org.rifidi.edge.core.configuration.services.ConfigurationService</tt> 
'''Methods''' 
*<tt>void storeConfiguration()</tt> - Store all configurations to persistence (i.e. xml file, database, etc).
*<tt>Configuration getConfiguration(String serviceID)</tt> - Get a configuration (i.e. Sensor Configuration or Command Configuration)by service ID.
*<tt>void createService(String factoryID, AttributeList attributes)</tt> - Create a new configuration using a factory with the supplied ID. Use the supplied AttributeList to override defaults.
*<tt>void destroyService(String serviceID)</tt> - Destroy a service with the supplied ID
*<tt>Set<Configuration> getConfigurations()</tt> - Return all Configurations.

===Sensor Management Service===
'''Purpose''': Since there is a concept of "Logical Sensors", it is possible to define a sensor that is a collection of physical sensors. This service allows sensors to be created, destroyed, grouped as part of a logical sensor, and subscribed to 
'''Interface''': <tt>org.rifidi.edge.core.sensors.management.SensorManagementService</tt> 
'''Methods''' 
*<tt>void createSensor(String sensorName)</tt> - Create a new sensor with the given name
*<tt>void destroySensor(String sensorName)</tt> - Destroy a sensor with the given name
*<tt>void createSensor(String sensorName, Collection<String> childSensors)</tt> - Create a new sensor with the given name and has the given child sensors
*<tt>void renameSensor(String oldName, String newName)</tt> - Rename a sensor
*<tt>void addChild(String sensorName, String childName)</tt> - Add the child sensor to this logical sensor
*<tt>void addChildren(String sensorName, Collection<String> childNames)</tt> - Add multiple children to this logical sensor
*<tt>void setChildren(String sensorName, Collection<String> childNames)</tt> - Set the children of this logical sensor to the supplied list
*<tt>void removeChild(String sensorName, String childName)</tt> - Remove the given child sensor from this logical sensor
*<tt>void removeChildren(String sensorName, Collection<String> childrenNames)</tt> - Remote all the given child sensors from this logical sensor
*<tt>Sensor subscribe(Object subscriber, String sensorName)</tt> - Subscribe an object to the sensor
*<tt>void unsubscribe(Object subscriber, String sensorName)</tt> - Unsubscribe an object from the sensor
*<tt>void publishToEsper(String sensorName)</tt> - Publish all tags produced by this sensor to esper under the given sensorName
*<tt>void unpublishFromEsper(String sensorName)</tt> - Stop publishing tags produced by this sensor to esper under the given SensorName
*<tt>SensorDTO getDTO(String sensorName)</tt> - Get the Data Transfer Object of the sensor with the given name
*<tt>Set<String> getSensors()</tt> - Get a list of all children sensors belonging to this one.

===JMX Service===
'''Purpose''': Exposes a Configuration via JMX 
'''Interface''': <tt>org.rifidi.edge.core.configuration.services.JMXService</tt> 
'''Methods''' 
*<tt>void publish(Configuration config)</tt> - Publishes the given Configuration to JMX
*<tt>void unpublish(Configuration config)</tt> - Removes the given Configuration from JMX
*<tt>public void setConfigurationControlMBean(ConfigurationControlMBean mbean)</tt>

==JMS Services==
The Edge server uses JMS internally to pass events. To learn how JMS is configured inside of the edge server, see [[EdgeServerJMS| JMS in the Edge Server]]. The following services are preconfigured JMS components that facilitate using JMS in other areas of the edge server. They are created and made available in the jms bundle
===Internal Destination===
'''Purpose''': A JMS Topic that serves as an internal high-speed message bus. Sensors will place tag reads on it. 
'''Interface''': <tt>javax.jms.Topic</tt> 
===External Tags Destination===
'''Purpose''': A JMS Topic that serves as destination for clients that run outside the edge server's JVM to receive tag reads. 
'''Interface''': <tt>javax.jms.Topic</tt> 
===External Notification Destination===
'''Purpose''': A JMS Topic that serves as destination for clients that run outside the edge server's JVM to receive notification events, such as when a sensor is created or deleted, or a session has been started or stopped. 
'''Interface''': <tt>javax.jms.Topic</tt> 
===Internal Broker Connection Factory===
'''Purpose''': A JMS Connection Factory that creates connections to the internal ActiveMQ Broker. 
'''Interface''': <tt>javax.jms.ConnectionFactory</tt> 
===External Broker Connection Factory===
'''Purpose''': A JMS Connection Factory that creates connections to the external ActiveMQ Broker. 
'''Interface''': <tt>javax.jms.ConnectionFactory</tt> 
===Internal JMS Template===
'''Purpose''': A Spring object that makes it easier to send messages to the internal broker 
'''Interface''': <tt>org.springframework.jms.core.JmsTemplate</tt> 
===External JMS Template===
'''Purpose''': A Spring object that makes it easier to send messages to the external broker 
'''Interface''': <tt>org.springframework.jms.core.JmsTemplate</tt> 

==Other Services==
There are a few other services that are important. The interfaces for these services can be found in the edge server services bundle, and each service will be implemented in its own bundle.
===Esper Management Service===
'''Purpose''': Provides access to esper 
'''Interface''': <tt>org.rifidi.edge.core.services.esper.EsperManagementService</tt> 
'''Methods''': 
*<tt>EPServiceProvider getProvider()</tt> - Get the EsperServiceProvider so that you can use esper.
===Notification Service===
'''Purpose''': Allows the edge server to notify external clients when an important state change happens (such as when a sensor configuration is created or when a sensor session is started). These methods should be called on this service when the corresponding event happens. For example, when a session is created, the addSessionEvent() method should be called. 
'''Interface''': <tt>org.rifidi.edge.core.services.notification.NotificationService</tt> 
'''Methods''': 
*<tt>void addSessionEvent(String readerID, String sessionID)</tt>
*<tt>void removeSessionEvent(String readerID, String sessionID)</tt>
*<tt>void addReaderEvent(String readerID)</tt>
*<tt>void removeReaderEvent(String readerID)</tt>
*<tt>void removeReaderEvent(String readerID)</tt>
*<tt>void addCommandEvent(String commandID)</tt>
*<tt>void removeCommandEvent(String commandID)</tt>
*<tt>void addReaderFactoryEvent(String readerFactoryID)</tt>
*<tt>void removeReaderFactoryEvent(String readerFactoryID)</tt>
*<tt>void sessionStatusChanged(String readerID, String sessionID,SessionStatus sessionStatus)</tt>
*<tt>void addCommandConfigFactoryEvent(String readerFactoryID,String commandConfigFactoryID)</tt>
*<tt>removeCommandConfigFactoryEvent(String readerFactoryID,String commandFactoryID)</tt>
*<tt>void jobSubmitted(String readerID, String sessionID, Integer jobID, String commandID)</tt>
*<tt>jobDeleted(String readerID, String sessionID, Integer jobID)</tt>
*<tt>attributesChanged(String configurationID, AttributeList attributes)</tt>

===Logging Service===
'''Purpose''': Allows the logging level to be changed at runtime. For more information, see [[How to change logging levels]] 
'''Interface''': <tt>org.rifidi.edge.core.services.logging.LoggingService</tt> 
'''Methods''': 
*<tt>setLoggingLevel(String loggerName, String level)</tt> - Change the logging level of the logger (class or package name) to the given logging level.

=Core Bundles=
The edge server is deployed as a set of OSGi bundles. The following bundles make up the core.
;org.rifidi.edge.api
: Provides core classes that are necessary for an outside UI to talk to the edge server via RMI and JMS, such as Data Transfer Objects (DTOs), JMS Notification Messages, RMI Interfaces, and Tag Messages.
;org.rifidi.edge.console
: Provides the ability to control the edge server using the OSGi console provided by eclipse equinox. For more information about how to control the console, see [[Edge_Server_Console]].
;org.rifidi.edge.core
: Provides configuration & persistence, Management of reader and command configurations, Abstract classes and interfaces for sensor plugins to implement, and Esper,
;org.rifidi.edge.core.rmi.server
: Exposes core functionality via RMI for outside clients (especially UIs) to use to control the edge server. It exposes roughly the same functionality as the console. For more information about how to expose a service using RMI see: [[How to export a service using RMI]]
;org.rifidi.edge.core.services
: Contains the interfaces for several OSGi services used within the edge sever
;org.rifidi.edge.core.jms
:Configures JMS for the edge server. See [[EdgeServerJMS]] for more details
;org.rifidi.edge.core.services.logging
:Provides a service to modify the logging level at run time
;org.rifidi.edge.core.services.notifications
:Provides a service to notify external clients (such as UIs) about state changes inside the edge server

=Important Dependencies=
==Spring==
===Spring DM===
==SLF4J==
==Esper==
==ActiveMQ==

Edge Server Architecture

2011-11-01T04:54:07Z

Seoagent: /* Communication Layer */

This page describes several aspects of the Rifidi Edge Server Core. It is intended for developers to understand how the core is structured.
=Overview=
There are two main aspects to understanding the edge server. The first is the three architectural layers that facilitate the flow of data from sensor to a designated endpoint. The second is the runtime and how it uses service oriented architecture and OSGi to be dynamic and light weight.
==Layers==
This section shows the three conceptual architectural layers that data passes through on its journey from sensors to whatever endpoint the user chooses.

[[Image:Dataflow3.png|thumbnail|400px|Dataflow through the three Architectural layers in the Rifidi Edge Server]]

===Sensor Abstraction Layer===
The purpose of the edge server is to connect to any kind of sensors (e.g. RFID readers, Barcode readers, Mobile Devices) and collect information from them. In many scenarios, this consists of connecting to a Gen2 fixed reader (such as Alien 9800, Motorolla LLRP, etc), and collecting EPC information. However, the edge server is designed in a way so that the edge server to collect many kinds of data (active, passive, etc) from many kinds of devices. This layer allows users to connect to devices in a sensor-agnostic way to collect the kind of data required for the application.

===Application Engine Layer===
For most applications it is not desirable to save every event that the sensors produce. Many sensors can send 1,000 of events a second, a large number of which might be duplicates. Most applications are interested in events that are one-level higher than the raw events produced by sensors. For examples, an ERP system is probably interested in the event of a box arriving in area 1, and it is not desirable for the ERP system to do the work of filtering and processing all of duplicate reads the sensor produces.

Complex Event Processing (CEP) is a paradigm of viewing data as ephemeral events (an event stream) and identifying meaningful (i.e. business) events from the stream using rules. Rifidi Edge Server uses a Complex Event Processor called Esper. It allows you to write queries using an SQL-like syntax:
<pre>
select * from ReadCycle where ReaderID='gate_1'
</pre>

One of the most important aspects of CEP is being able to use incorporate temporal knowledge into the queries. This allows you to phrase queries like "Send an order_complete event when an itemA event is followed by an itemb event" or "send an order_cancelled event when an itemb event is not seen within 10 min of a itemA event."

The Application Engine Layer is intended to let application developers build much of the functionality of their RFID applications using esper queries.

===Communication Layer===
After data has been processed, it probably needs to be handed up to some kind of application-dependent system. For example, some users might want the data to be stored in an [http://physioactive.sg/ massage therapy singapore] database, others might want it to be pushed into an ERP system like SAP or handed to a [http://www.inleds.com/products/?cid=2 led downlight singapore] Rich User Interface of some sort. The edge server has several built in connectors to use, namely JMS and Web Services (via Spring's remoting framework). However, as this is application dependant, it is possible to write your own connector (such as a TCP/IP socket connection) if the application needs it.

In addition, the edge server also provides a [http://www.inleds.com/ singapore led lighting] built-in web container and MVC framework so that web applications can be deployed directly.

==OSGi==
OSGi is a dynamic modules system for Java. It provides several pieces of functionality including the following:
# A deployment unit (called a bundle), which is a normal JAR with some extra information in the Manifest.
# A lightweight runtime that allows bundle lifecycle to be controlled. In other words, you can start, stop, and update bundles at runtime.
# Dependencies are explicitly stated in the Manifest either as "bundle dependencies" or "package dependencies".
# Classes are only visible to other bundles if their containing packages have been exposed. This allows developers to hide classes that should be strictly internal.
# The runtime provides a service registry -- a system-wide repository for bundles to provide functionality.

The edge server is simply a collection of bundles that run in an OSGi environment (Equinox). Functionality between bundles is shared by means of services that are available in the service registry. Because bundles can be started and stopped while the rest of the server is still running, we can update non-essential parts of the edge server without restarting it.

=Services=
In the Edge Server, services are POJOs that provide a specific piece of functionality to other components and are registered in the OSGi Registry. For more information see [[How to use OSGi Services]]
== Core Services==
The following services are provided by the core bundle.
===Reader Data Access Object===
'''Purpose''': Provide access to sensor configurations that have been created. 
'''Interface''': <tt>org.rifidi.edge.core.daos.ReaderDAO</tt> 
'''Methods''' 
* <tt>Set<AbstractSensor> getReaders()</tt> Get all available sensor configurations
* <tt>AbstractSensor getReaderByID(String ID)</tt> - Get the sensor with the supplied ID
* <tt>Set<AbstractSensorFactory> getReaderFactories()</tt> - Get all registered sensor factories
* <tt>AbstractSensorFactory getReaderFactoryByID()</tt> - Get the sensor factory with the supplied ID
===Command Data Access Object===
'''Purpose''': Provide access to command configurations that have been created. 
'''Interface''': <tt>org.rifidi.edge.core.daos.CommandDAO</tt> 
'''Methods''' 
* <tt>Set<AbstractCommandConfiguration> getCommands()</tt> Get all available command configurations
* <tt>AbstractCommandConfiguration getCommandByID(String ID)</tt> - Get the command configuration with the supplied ID
* <tt>Set<AbstractCommandConfigurationFactory> getCommandFactories()</tt> - Get all registered command configuration factories
* <tt>AbstractCommandConfigurationFactory getCommandFactoryByID(String ID)</tt> - Get the command configuration factory with the supplied ID
* <tt>AbstractCommandConfigurationFactory getCommandFactoryByReaderID(String ID)</tt> - Get the command configuration factory with the supplied sensor ID

===Configuration Service===
'''Purpose''': Provide a way to save and load configurations from persistence. Configurations (such as Sensor Configurations or Command Configurations) are created using a factory (that must be registered). Configurations have Attributes which can be changed via getters and setters. 
'''Interface''': <tt>org.rifidi.edge.core.configuration.services.ConfigurationService</tt> 
'''Methods''' 
*<tt>void storeConfiguration()</tt> - Store all configurations to persistence (i.e. xml file, database, etc).
*<tt>Configuration getConfiguration(String serviceID)</tt> - Get a configuration (i.e. Sensor Configuration or Command Configuration)by service ID.
*<tt>void createService(String factoryID, AttributeList attributes)</tt> - Create a new configuration using a factory with the supplied ID. Use the supplied AttributeList to override defaults.
*<tt>void destroyService(String serviceID)</tt> - Destroy a service with the supplied ID
*<tt>Set<Configuration> getConfigurations()</tt> - Return all Configurations.

===Sensor Management Service===
'''Purpose''': Since there is a concept of "Logical Sensors", it is possible to define a sensor that is a collection of physical sensors. This service allows sensors to be created, destroyed, grouped as part of a logical sensor, and subscribed to 
'''Interface''': <tt>org.rifidi.edge.core.sensors.management.SensorManagementService</tt> 
'''Methods''' 
*<tt>void createSensor(String sensorName)</tt> - Create a new sensor with the given name
*<tt>void destroySensor(String sensorName)</tt> - Destroy a sensor with the given name
*<tt>void createSensor(String sensorName, Collection<String> childSensors)</tt> - Create a new sensor with the given name and has the given child sensors
*<tt>void renameSensor(String oldName, String newName)</tt> - Rename a sensor
*<tt>void addChild(String sensorName, String childName)</tt> - Add the child sensor to this logical sensor
*<tt>void addChildren(String sensorName, Collection<String> childNames)</tt> - Add multiple children to this logical sensor
*<tt>void setChildren(String sensorName, Collection<String> childNames)</tt> - Set the children of this logical sensor to the supplied list
*<tt>void removeChild(String sensorName, String childName)</tt> - Remove the given child sensor from this logical sensor
*<tt>void removeChildren(String sensorName, Collection<String> childrenNames)</tt> - Remote all the given child sensors from this logical sensor
*<tt>Sensor subscribe(Object subscriber, String sensorName)</tt> - Subscribe an object to the sensor
*<tt>void unsubscribe(Object subscriber, String sensorName)</tt> - Unsubscribe an object from the sensor
*<tt>void publishToEsper(String sensorName)</tt> - Publish all tags produced by this sensor to esper under the given sensorName
*<tt>void unpublishFromEsper(String sensorName)</tt> - Stop publishing tags produced by this sensor to esper under the given SensorName
*<tt>SensorDTO getDTO(String sensorName)</tt> - Get the Data Transfer Object of the sensor with the given name
*<tt>Set<String> getSensors()</tt> - Get a list of all children sensors belonging to this one.

===JMX Service===
'''Purpose''': Exposes a Configuration via JMX 
'''Interface''': <tt>org.rifidi.edge.core.configuration.services.JMXService</tt> 
'''Methods''' 
*<tt>void publish(Configuration config)</tt> - Publishes the given Configuration to JMX
*<tt>void unpublish(Configuration config)</tt> - Removes the given Configuration from JMX
*<tt>public void setConfigurationControlMBean(ConfigurationControlMBean mbean)</tt>

==JMS Services==
The Edge server uses JMS internally to pass events. To learn how JMS is configured inside of the edge server, see [[EdgeServerJMS| JMS in the Edge Server]]. The following services are preconfigured JMS components that facilitate using JMS in other areas of the edge server. They are created and made available in the jms bundle
===Internal Destination===
'''Purpose''': A JMS Topic that serves as an internal high-speed message bus. Sensors will place tag reads on it. 
'''Interface''': <tt>javax.jms.Topic</tt> 
===External Tags Destination===
'''Purpose''': A JMS Topic that serves as destination for clients that run outside the edge server's JVM to receive tag reads. 
'''Interface''': <tt>javax.jms.Topic</tt> 
===External Notification Destination===
'''Purpose''': A JMS Topic that serves as destination for clients that run outside the edge server's JVM to receive notification events, such as when a sensor is created or deleted, or a session has been started or stopped. 
'''Interface''': <tt>javax.jms.Topic</tt> 
===Internal Broker Connection Factory===
'''Purpose''': A JMS Connection Factory that creates connections to the internal ActiveMQ Broker. 
'''Interface''': <tt>javax.jms.ConnectionFactory</tt> 
===External Broker Connection Factory===
'''Purpose''': A JMS Connection Factory that creates connections to the external ActiveMQ Broker. 
'''Interface''': <tt>javax.jms.ConnectionFactory</tt> 
===Internal JMS Template===
'''Purpose''': A Spring object that makes it easier to send messages to the internal broker 
'''Interface''': <tt>org.springframework.jms.core.JmsTemplate</tt> 
===External JMS Template===
'''Purpose''': A Spring object that makes it easier to send messages to the external broker 
'''Interface''': <tt>org.springframework.jms.core.JmsTemplate</tt> 

==Other Services==
There are a few other services that are important. The interfaces for these services can be found in the edge server services bundle, and each service will be implemented in its own bundle.
===Esper Management Service===
'''Purpose''': Provides access to esper 
'''Interface''': <tt>org.rifidi.edge.core.services.esper.EsperManagementService</tt> 
'''Methods''': 
*<tt>EPServiceProvider getProvider()</tt> - Get the EsperServiceProvider so that you can use esper.
===Notification Service===
'''Purpose''': Allows the edge server to notify external clients when an important state change happens (such as when a sensor configuration is created or when a sensor session is started). These methods should be called on this service when the corresponding event happens. For example, when a session is created, the addSessionEvent() method should be called. 
'''Interface''': <tt>org.rifidi.edge.core.services.notification.NotificationService</tt> 
'''Methods''': 
*<tt>void addSessionEvent(String readerID, String sessionID)</tt>
*<tt>void removeSessionEvent(String readerID, String sessionID)</tt>
*<tt>void addReaderEvent(String readerID)</tt>
*<tt>void removeReaderEvent(String readerID)</tt>
*<tt>void removeReaderEvent(String readerID)</tt>
*<tt>void addCommandEvent(String commandID)</tt>
*<tt>void removeCommandEvent(String commandID)</tt>
*<tt>void addReaderFactoryEvent(String readerFactoryID)</tt>
*<tt>void removeReaderFactoryEvent(String readerFactoryID)</tt>
*<tt>void sessionStatusChanged(String readerID, String sessionID,SessionStatus sessionStatus)</tt>
*<tt>void addCommandConfigFactoryEvent(String readerFactoryID,String commandConfigFactoryID)</tt>
*<tt>removeCommandConfigFactoryEvent(String readerFactoryID,String commandFactoryID)</tt>
*<tt>void jobSubmitted(String readerID, String sessionID, Integer jobID, String commandID)</tt>
*<tt>jobDeleted(String readerID, String sessionID, Integer jobID)</tt>
*<tt>attributesChanged(String configurationID, AttributeList attributes)</tt>

===Logging Service===
'''Purpose''': Allows the logging level to be changed at runtime. For more information, see [[How to change logging levels]] 
'''Interface''': <tt>org.rifidi.edge.core.services.logging.LoggingService</tt> 
'''Methods''': 
*<tt>setLoggingLevel(String loggerName, String level)</tt> - Change the logging level of the logger (class or package name) to the given logging level.

=Core Bundles=
The edge server is deployed as a set of OSGi bundles. The following bundles make up the core.
;org.rifidi.edge.api
: Provides core classes that are necessary for an outside UI to talk to the edge server via RMI and JMS, such as Data Transfer Objects (DTOs), JMS Notification Messages, RMI Interfaces, and Tag Messages.
;org.rifidi.edge.console
: Provides the ability to control the edge server using the OSGi console provided by eclipse equinox. For more information about how to control the console, see [[Edge_Server_Console]].
;org.rifidi.edge.core
: Provides configuration & persistence, Management of reader and command configurations, Abstract classes and interfaces for sensor plugins to implement, and Esper,
;org.rifidi.edge.core.rmi.server
: Exposes core functionality via RMI for outside clients (especially UIs) to use to control the edge server. It exposes roughly the same functionality as the console. For more information about how to expose a service using RMI see: [[How to export a service using RMI]]
;org.rifidi.edge.core.services
: Contains the interfaces for several OSGi services used within the edge sever
;org.rifidi.edge.core.jms
:Configures JMS for the edge server. See [[EdgeServerJMS]] for more details
;org.rifidi.edge.core.services.logging
:Provides a service to modify the logging level at run time
;org.rifidi.edge.core.services.notifications
:Provides a service to notify external clients (such as UIs) about state changes inside the edge server

=Important Dependencies=
==Spring==
===Spring DM===
==SLF4J==
==Esper==
==ActiveMQ==

Alien 9800

2011-11-01T04:52:51Z

Seoagent: /* Autonomous Mode */

[[Category:developerDoc]][[Category:EmulatorDoc]][[Category:userDoc]]

==Introduction==
The Alien 9800 is produced by Alien Technology. It is a general purpose reader that can read Class 1 Gen 2 tags. For an introduction on how to use the Alien reader see the [[Alien_Beginners_Guide |Alien Beginner's Guide]]

;Model Number:
:ALR 9800
;Network Protocol:
:TCP/IP
;Communication:
:LAN TCP/IP(RJ-45), RS-232
;Antennas:
:4 ports
;General Purpose I/O:
: 4 Inputs, 8 Outputs

===Historical Note===
The Alien reader was the first reader that Pramari implemented, so therefore some of code in the emulator (such as the timestamp information in the tags and the tag memory) is alien specific. For more information about the structure of the emulator see [[Engine Overview]].

==Basis of Virtual Reader==
The implementation of the virtual reader is based on the testing of an actual hardware reader. Testing was done using wireshark to capture the client-reader communication. This input output was then emulated.
===Documentation===
There is not a lot of documentation freely available, as it is not on Alien's website. Documentation for this reader is bundled with the reader, so it can only be obtained by actually purchasing a reader. However, some universities may have documentation available for use by its students.
===Client Tools===
The main client tools used for testing this program:
;Alien Tool
:The Alien Tool is a client program that ships with the reader. It has an interesting look and feel. Its tag grid mode is useful to determine if a reader is properly reading tags.
;BEA 2.2
:[[BEA]] is a commercial edgeware application. It communicates with the alien reader via "on demand" mode. The new version of BEA (version 3.0), also has an option to use autonomous mode to get tag reads
;Logic Alloy 1.0.10
:[[Logic Alloy]] ALE Server is an open source edgeware application. It uses the alien reader's autonomous mode to obtain tag reads
;TagCentric
:[[TagCentric]] is an open source edgeware application that communicates with the alien reader via "on demand" commands.
;Example Client
:[[Alien Example Client]] shows how to connect to the alien reader using a simple java client.

==Reader Design==
This section will give a brief overview of how the hardware reader operates for the purposes of emulation.
===Communication===
The Alien reader sends plain text messages over a TCP connection. The connection can be easily tested by telnetting into the reader and issuing commands. The following is an example of a telnet session and getting the tag list. The reader is running at 192.168.2.100:20000.

<code><pre>$ telnet 192.168.2.100 20000
Trying 192.168.2.100...
Connected to 192.168.2.100.
Escape character is '^]'.
***********************************************
*
* Alien Technology : RFID Reader
*
***********************************************

Username>alien
alien

Password>password
********

Alien >get taglist
get taglist
(No tags)

Alien >

</pre></code>

When connecting programatically, it is useful to supress the prompt. This is done by prepending a 0x01 to the beginning of the text to be sent. Also keep in mind that all commands are terminated by a carriage return and a line feed (0x0d 0x0a)

===Memory Model===
The memory model of the alien reader is based on the concept of persist time, which is the amount of time a tag stays in memory after having been seen by an antenna. It is possible to change the persist time using the <code>set persistTime</code> command. For example, the following command will set the persist time to 500 ms.
<code><pre>Alien >set persistTime=500
set persistTime
PersistTime = 500</pre></code>

If the persistTime is set to a -1, the tag will persist in memory until a <code>get tagList</code> operation is performed (either on-demand or autonomously).

===Getting Tags===
There are two main modes to get tags from an alien reader. The simplest is "on demand" mode, in which the user simply issues a command and the reader sends back a tag list. The Autonomous mode enables the reader to act as a client and send tag lists to a server at some location.
====On Demand====
To get tag reads in On Demand read, a user can send a 'get taglist' command, or more simply 't'. The reader will respond with its tag list.
====Autonomous Mode====
Autonomous mode is more complicated. A user will set up several parameters, such as the notifyAddress (the address of the server where tag lists are to be sent), notifyTime (a time interval a which messages will be sent), notifyTrigger (a condition upon which to fire a message), and others. When a trigger is fired, or the notify time has expired, a message that contains the tag list will be sent to the server.

The interaction between AutoMode and NotifyMode is [http://physioactive.sg/services/massage/sports-massage.html sports massage singapore] important to understand. If AutoMode is on, but NotifyMode is off, no messages will be sent. If NotifyMode is on but AutoMode is off, messages will be sent containing blank TagLists.

Autonomous mode messages consist of an optional header (controlled by the NotifyHeader variable) followed by a list of tags which were read. The message format (controlled by the NotifyFormat variable) can be xml, terse, string, or custom.

The NotifyTime is a [http://physioactive.sg/services/sports-therapy.html sports injury singapore] variable that controls how often time-based messages are sent, and is specified in seconds. If set to zero, automatic, time-based notification is disabled. The tags contained in each message are the tags in the TagList (i.e. the reader's tag memory) at the time the message was fired; the reader essentially gets the TagList (in the same way that a user could in interactive mode by typing “get TagList”) at regular intervals and puts the results in a message.

===Login===
The Alien Reader requires the user to log in. The default name and password is "alien/password".

==Supported Features==

The following is a list of important features of the Alien reader that are properly emulated by Rifidi

===Login===

It is possible to log into the alien reader with a username and password. The alien reader will not work until you are logged in.

===Getting and Setting variables===

The rifidi Alien reader allows users to get and set all variables, using the <code>get</code> and <code>set</code> commands.

===Getting TagList===

As mentioned previously, it is possible to get the tag list using the <code>get taglist</code> or the <code>t</code> command.

===Persist Time===

The persist time controls how long a tag resides in memory before it is deleted. It works except for a bug if the peresttime=-1 as explained below

===Autonomous Mode===

Most of the autonomous mode works except that notifyTrigger only works properly when set to <code>truefalse</code>, and does not properly emulate the other possible values for it.

===Supported Commands===
A list of commands supported by rifidi:

====General Commands====
*Quit (q)
*get/set ReaderName
*get ReaderType
*get ReaderVersion
*get / set ReaderNumber
*get / set Username
*get / set Password

====TagList Commands====
*get Taglist (t)
*get / set PersistTime
*get / set TagListFormat (possible values = text, terse, xml)
*clearTagList
*get / set TagType

====Radio Commands====
*get / set AntennaSequence

====Autonomous Commands====
*get / set AutoMode (possible values = on, off)
*get / set AutoFalseOutput
*get / set AutoFalsePause
*get / set AutoStartPause
*get / set AutoStartTrigger
*get / set AutoStopTimer
*get / set AutoStopTrigger
*get / set AutoStopTimer
*get / set AutoTrueOutput
*get / set AutoTruePause
*get / set NotifyMode
*get / set NotifyAddress
*get / set NotifyFormat (possible values = text, terse, xml)
*get / set NotifyTime
*get / set NotifyTrigger
*get / set NotifyHeader (possible values = on, off)

====Program Tag Commands====
*get / set ProgAntenna
*ProgramTag
*get / set Function

====GPIO Commands====
*get / set ExternalOutput

==Bugs and Unsupported Features==

Rifidi:Source Code

2011-11-01T04:51:43Z

Seoagent: /* Running Rifidi */

[[category:developerDoc]]
This page explains how to download and run the source code for the Rifidi products. However, please keep in mind that the code in this repository is not guaranteed to be stable. If you are interested in our latest stable release, visit our sourceforge page: http://sourceforge.net/projects/rifidi/.
=Quick Instructions=
The following are the basic steps needed to begin running Rifidi from source. If you have trouble or need more explanation, please see the more detailed instructions on this page.
# Download the Eclipse for plugin developers (3.5 is what we are using)
# Install the subclipse plugin
# Add this svn to the list of repositories: https://svn.rifidi.org/svn/rep-external
# Check out the following projects from rifidi/trunk: org.rifidi.binary, org.rifidi.emulator.target, org.rifidi.ui.ide
# Open up the target file in org.rifidi.emulator.target and click the button that says "set as target platform"
# Open up the .product file in org.rifidi.ui.ide and click "launch an eclipse application"

=Weekly Builds=
Because many of our users are intereted in running the latest version of the Rifidi products but don't want to go to all the trouble of downloading the source code, there is a weekly build of the products. The weekly builds include the latest features, but is not as tested as the sourceforge releases. A link will be provided soon.
=Rifidi Source Code=
For those who need to see the source code for the Rifidi products, you will have to check out the code from svn. This section explains how to check out and run the code from source.
==Organization==
In general the code for Rifidi is organized into Eclipse plugins or bundles. Eclipse handles the loading and execution of the plugins. For more detailed information about how our source code is organized, please see [[Development and Release Process#Concepts]].
* '''SVN Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi). The ''trunk'' folder contains the code that is being developed. It is ''not'' guaranteed to be stable. The ''tags'' folder contains tagged versions of the source for each of [http://www.timewing.com.sg/ aircon service] the plugins. The source in these plugins should be relatively stable. The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers. These changes can then later be merged back in. For more details about our SVN, see [[Development and Release Process#SVN Structure]]
* Target Platform - A target platform is the base set of [http://www.timewing.com.sg/ac_service.html ac repair] plugins that an Eclipse application needs to run. In order to provide a more stable environment and to ensure a clean separation between the base plugins that Rifidi needs and the base plugins that your Eclipse IDE needs, we provide a target platform for each of the Rifidi products. You can find these in the trunk. They will be named something like <code>org.rifidi.emulator.target</code>. For more information see [[Development and Release Process#Target Platforms]].
* org.rifidi.binary - As the source code for Rifidi gets larger it begins to get harder to maintain a stable set of plugins. In order to simplify things, there is a folder in the [http://www.timewing.com.sg/refrg_service.html refrigerator repair] svn into which stable binaries of each of the plugins used in the rifidi project will be placed. This folder is used in conjunction with the target platform.
* Product File - In Eclipse, a product file is used to define the needed eclipse plugins. Running this file will create a new Eclipse 'Run Configuration' in your IDE. You can then tweak this run configuration as needed.
* Source Code Plugins - A stable binary version of each of the plugins is [http://jamumassagesingapore.com/services/dejamu/post-natal jamu postnatal massage] contained in the org.rifidi.binary folder. However, if you wish to view the source of a particular plugin or run a plugin from source, you must download the code from either the version in the trunk or a tagged version in the tags directory.

==Downloading the Code==

Our code is hosted at https://svn.rifidi.org/svn/rep-external. The svn repository allows anonymous read access. Because the svn repository is the same one that developers submit to, it contains the latest Rifidi code.

The following steps explain how to check out and run Rifidi Emulator. The other products in the Rifidi Suite follow similar steps. If you need help with them, you can ask questions on IRC or our forums.

===Prerequisites===

The Rifidi Emulator is written in java and consists of Eclipse plugins. At this point it is easiest to compile and build it inside of the eclipse environment.

====Install Eclipse====
Note that you need the "Eclipse for RCP/Plug-in Developers" version of eclipse. Rifidi will not run on other versions.
* If you do not already have eclipse, or if you have a different version, you will need to get this version
** Go to http://www.eclipse.org/downloads/ and download the "Eclipse for RCP/Plug-in Developers" version of Eclipse to a convenient location.
** Unzip the package.
** Double click on the execution file to get it started [[Image:Rifidi_from_source-1-opening_eclipse.png |none|thumb|800px|Double click on the executable to open up eclipse]]
* If you have not used eclipse before, you will be required to select a workspace when eclipse is opening.
** After eclipse opens go to the workbench[[Image:Rifidi_from_source-2-wokbench.png |none|thumb|800px|Open up the workbench]]
* If you have an existing workspace, you will need to create a new one.
** Go to file -> switch workspace -> other [[Image:Rifidi_from_source-3-switch_workspace.png |none|thumb|800px|Open up the workbench]]
** Select a new directory for your Rifidi workspace.

====Install Subclipse====

Subclipse is an eclipse plugin that manages svn commands.

* Follow the instructions at http://subclipse.tigris.org/install.html.
* In step 6 of the above instructions, don't install the Optional Integrations. Only the subclipse plugin is needed

===Add Repository===

* Open the 'SVN Repository Exploring' perspective
** Window -> Open Perspective -> Other [[Image:Rifidi_from_source-4-svn_rep_explore1.png |none|thumb|800px|Open up the perspective picker]]
** SVN Repository Exploring [[Image:Rifidi_from_source-5-svn_rep_explore2.png |none|thumb|400px|Open up the SVN Repository Explorer]]
* Add the rifidi repository
** Click 'Add SVN Repository' button
** Add 'https://svn.rifidi.org/svn/rep-external'[[Image:Rifidi_from_source-6-add_rep.png |none|400px|thumb|Add the repository]]

===Check Out Code===

* Check out all the projects in the rifidi/trunk folder of the repository
** Highlight the folders you would like to check out. For Emulator you will need
*** <code>org.rifidi.binary</code>
*** <code>org.rifidi.emulator.taget3.5.2</code>
*** <code>org.rifidi.ui.ide</code>
** Right click them and select checkout [[Image:Rifidi_from_source-7-checkout1.png |none|800px|thumb|Select the projects]]
** Select Finish. [[Image:Rifidi_from_source-8-checkout2.png |none|400px|thumb|Checkout projects]]

===Set The Target Platform===
* Open up the .target file in <code>org.rifidi.emulator.target</code>
* Click the button that says "set as target platform"

==Running Rifidi==

The last step to get Rifidi running is to create a run configuration.

A run configuration is the set of plugins that will be loaded when you run the application. Plugins can come from one of two places:
#Workspace - these are the plugins that you have in the source tree on the left
#Target Environment - These are the plugins defined by the target environment that you are using that the time.

Because there is a product file [http://jamumassagesingapore.com massage centres in singapore] for emulator defined in the <code>org.rifidi.ui.ide</code> plugin, the easiest way to create a new run configuration is by running the product file. This will automatically create a new run configuration

To Create a new Run Configuration:
* Switch to the Java perspective in the same way [http://jamumassagesingapore.com/services/pre-natal prenatal massage in singapore] that you switched to the repository exploring view [[Image:Rifidi_from_source-9-java_view.png |none|400px|thumb|Run Rifidi]]
* Right click on Rifidi.product in the org.rifidi.ui.ide project
* Click on "Run as eclipse application" [[Image:Rifidi_from_source-10_run_eclipse.png |none|thumb|800px|Run Rifidi]]
* From now on, you can start Rifidi via the green triangle button at the top of eclipse

If there was an error when starting the application, follow the step below to edit the run configuration:

To Edit a Run Configuration:
* Run -> Open Run Dialog -> Eclipse Application -> Rifidi.product. This is the run configuration.
* Go to the Tab Plug-ins. The selected plugins are the ones that will be run. Notice that there are two sections: "workspace" and "target platform"
* click the Button "Add Required Plug-ins" [[Image:Rifidi_from_source-11_add_plugins.png |none|thumb|600px|Add required plugins]]
* check any plugins specifically required for the application to run (for example, the emulator requires the readers to be included). Make sure that the plugin is coming from the place [http://www.miiny.com deals singapore] that you intended (i.e. workspace or target platform).
* click the Button "Validate Plug-ins" to make sure everything is set up correctly
* click the Button "Apply"
* click the Button "Run" and start the Project

==Updating the code==

Now that you have downloaded the code into an eclipse workspace, it is easy to get changes to the code as soon as we add them to the svn.

To update the code:

* Open up the Team Synchronizing Perspective in eclipse
* Click the button that says "Synchronize".
* Select all projects.
* Install any updates by selecting all the updates show, right clicking and choosing 'update'

Now that you have the new code, just hit the green run button on the toolbar at the top (Eclipse automatically compiles the code for you, so you don't have to worry about that).

==Switching Branches==
If you need to run code from another branch or tag, please see [[Switching Branches]].

==Viewing Source and Running From Trunk==
By default all of the rifidi plugins you are running in eclipse are pre-compiled, binary plugins contained in the <code>org.rifidi.binary</code> folder. If you want to view or edit the source for a particular plugin, you will need to check out the plugin from the trunk. Once it is checked out make sure to edit your run configuration so that the application will use the plugin from the workspace and not from the target platform.

For example, suppose I want to view the source for the Alien reader plugin. I need to follow the steps above to check out and run rifidi emulator. In addition, I need to check out the <code>org.rifidi.emulator.readers.alien</code> plugin. This is the code for the alien reader. In addition, I need to edit the run configuration to make sure that my workspace alien reader plugin is being used instead of the target platform alien reader plugin.

=Reporting Bugs=

To report bugs, please use the forum at

http://forums.rifidi.org

or drop by our IRC channel:

<nowiki>#rifidi on irc.freenode.org.</nowiki>

You can also visit us online at http://www.rifidi.org

Rifidi:Source Code

2011-11-01T04:50:48Z

Seoagent: /* Organization */

[[category:developerDoc]]
This page explains how to download and run the source code for the Rifidi products. However, please keep in mind that the code in this repository is not guaranteed to be stable. If you are interested in our latest stable release, visit our sourceforge page: http://sourceforge.net/projects/rifidi/.
=Quick Instructions=
The following are the basic steps needed to begin running Rifidi from source. If you have trouble or need more explanation, please see the more detailed instructions on this page.
# Download the Eclipse for plugin developers (3.5 is what we are using)
# Install the subclipse plugin
# Add this svn to the list of repositories: https://svn.rifidi.org/svn/rep-external
# Check out the following projects from rifidi/trunk: org.rifidi.binary, org.rifidi.emulator.target, org.rifidi.ui.ide
# Open up the target file in org.rifidi.emulator.target and click the button that says "set as target platform"
# Open up the .product file in org.rifidi.ui.ide and click "launch an eclipse application"

=Weekly Builds=
Because many of our users are intereted in running the latest version of the Rifidi products but don't want to go to all the trouble of downloading the source code, there is a weekly build of the products. The weekly builds include the latest features, but is not as tested as the sourceforge releases. A link will be provided soon.
=Rifidi Source Code=
For those who need to see the source code for the Rifidi products, you will have to check out the code from svn. This section explains how to check out and run the code from source.
==Organization==
In general the code for Rifidi is organized into Eclipse plugins or bundles. Eclipse handles the loading and execution of the plugins. For more detailed information about how our source code is organized, please see [[Development and Release Process#Concepts]].
* '''SVN Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi). The ''trunk'' folder contains the code that is being developed. It is ''not'' guaranteed to be stable. The ''tags'' folder contains tagged versions of the source for each of [http://www.timewing.com.sg/ aircon service] the plugins. The source in these plugins should be relatively stable. The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers. These changes can then later be merged back in. For more details about our SVN, see [[Development and Release Process#SVN Structure]]
* Target Platform - A target platform is the base set of [http://www.timewing.com.sg/ac_service.html ac repair] plugins that an Eclipse application needs to run. In order to provide a more stable environment and to ensure a clean separation between the base plugins that Rifidi needs and the base plugins that your Eclipse IDE needs, we provide a target platform for each of the Rifidi products. You can find these in the trunk. They will be named something like <code>org.rifidi.emulator.target</code>. For more information see [[Development and Release Process#Target Platforms]].
* org.rifidi.binary - As the source code for Rifidi gets larger it begins to get harder to maintain a stable set of plugins. In order to simplify things, there is a folder in the [http://www.timewing.com.sg/refrg_service.html refrigerator repair] svn into which stable binaries of each of the plugins used in the rifidi project will be placed. This folder is used in conjunction with the target platform.
* Product File - In Eclipse, a product file is used to define the needed eclipse plugins. Running this file will create a new Eclipse 'Run Configuration' in your IDE. You can then tweak this run configuration as needed.
* Source Code Plugins - A stable binary version of each of the plugins is [http://jamumassagesingapore.com/services/dejamu/post-natal jamu postnatal massage] contained in the org.rifidi.binary folder. However, if you wish to view the source of a particular plugin or run a plugin from source, you must download the code from either the version in the trunk or a tagged version in the tags directory.

==Downloading the Code==

Our code is hosted at https://svn.rifidi.org/svn/rep-external. The svn repository allows anonymous read access. Because the svn repository is the same one that developers submit to, it contains the latest Rifidi code.

The following steps explain how to check out and run Rifidi Emulator. The other products in the Rifidi Suite follow similar steps. If you need help with them, you can ask questions on IRC or our forums.

===Prerequisites===

The Rifidi Emulator is written in java and consists of Eclipse plugins. At this point it is easiest to compile and build it inside of the eclipse environment.

====Install Eclipse====
Note that you need the "Eclipse for RCP/Plug-in Developers" version of eclipse. Rifidi will not run on other versions.
* If you do not already have eclipse, or if you have a different version, you will need to get this version
** Go to http://www.eclipse.org/downloads/ and download the "Eclipse for RCP/Plug-in Developers" version of Eclipse to a convenient location.
** Unzip the package.
** Double click on the execution file to get it started [[Image:Rifidi_from_source-1-opening_eclipse.png |none|thumb|800px|Double click on the executable to open up eclipse]]
* If you have not used eclipse before, you will be required to select a workspace when eclipse is opening.
** After eclipse opens go to the workbench[[Image:Rifidi_from_source-2-wokbench.png |none|thumb|800px|Open up the workbench]]
* If you have an existing workspace, you will need to create a new one.
** Go to file -> switch workspace -> other [[Image:Rifidi_from_source-3-switch_workspace.png |none|thumb|800px|Open up the workbench]]
** Select a new directory for your Rifidi workspace.

====Install Subclipse====

Subclipse is an eclipse plugin that manages svn commands.

* Follow the instructions at http://subclipse.tigris.org/install.html.
* In step 6 of the above instructions, don't install the Optional Integrations. Only the subclipse plugin is needed

===Add Repository===

* Open the 'SVN Repository Exploring' perspective
** Window -> Open Perspective -> Other [[Image:Rifidi_from_source-4-svn_rep_explore1.png |none|thumb|800px|Open up the perspective picker]]
** SVN Repository Exploring [[Image:Rifidi_from_source-5-svn_rep_explore2.png |none|thumb|400px|Open up the SVN Repository Explorer]]
* Add the rifidi repository
** Click 'Add SVN Repository' button
** Add 'https://svn.rifidi.org/svn/rep-external'[[Image:Rifidi_from_source-6-add_rep.png |none|400px|thumb|Add the repository]]

===Check Out Code===

* Check out all the projects in the rifidi/trunk folder of the repository
** Highlight the folders you would like to check out. For Emulator you will need
*** <code>org.rifidi.binary</code>
*** <code>org.rifidi.emulator.taget3.5.2</code>
*** <code>org.rifidi.ui.ide</code>
** Right click them and select checkout [[Image:Rifidi_from_source-7-checkout1.png |none|800px|thumb|Select the projects]]
** Select Finish. [[Image:Rifidi_from_source-8-checkout2.png |none|400px|thumb|Checkout projects]]

===Set The Target Platform===
* Open up the .target file in <code>org.rifidi.emulator.target</code>
* Click the button that says "set as target platform"

==Running Rifidi==

The last step to get Rifidi running is to create a run configuration.

A run configuration is the set of plugins that will be loaded when you run the application. Plugins can come from one of two places:
#Workspace - these are the plugins that you have in the source tree on the left
#Target Environment - These are the plugins defined by the target environment that you are using that the time.

Because there is a product file for emulator defined in the <code>org.rifidi.ui.ide</code> plugin, the easiest way to create a new run configuration is by running the product file. This will automatically create a new run configuration

To Create a new Run Configuration:
* Switch to the Java perspective in the same way that you switched to the repository exploring view [[Image:Rifidi_from_source-9-java_view.png |none|400px|thumb|Run Rifidi]]
* Right click on Rifidi.product in the org.rifidi.ui.ide project
* Click on "Run as eclipse application" [[Image:Rifidi_from_source-10_run_eclipse.png |none|thumb|800px|Run Rifidi]]
* From now on, you can start Rifidi via the green triangle button at the top of eclipse

If there was an error when starting the application, follow the step below to edit the run configuration:

To Edit a Run Configuration:
* Run -> Open Run Dialog -> Eclipse Application -> Rifidi.product. This is the run configuration.
* Go to the Tab Plug-ins. The selected plugins are the ones that will be run. Notice that there are two sections: "workspace" and "target platform"
* click the Button "Add Required Plug-ins" [[Image:Rifidi_from_source-11_add_plugins.png |none|thumb|600px|Add required plugins]]
* check any plugins specifically required for the application to run (for example, the emulator requires the readers to be included). Make sure that the plugin is coming from the place that you intended (i.e. workspace or target platform).
* click the Button "Validate Plug-ins" to make sure everything is set up correctly
* click the Button "Apply"
* click the Button "Run" and start the Project

==Updating the code==

Now that you have downloaded the code into an eclipse workspace, it is easy to get changes to the code as soon as we add them to the svn.

To update the code:

* Open up the Team Synchronizing Perspective in eclipse
* Click the button that says "Synchronize".
* Select all projects.
* Install any updates by selecting all the updates show, right clicking and choosing 'update'

Now that you have the new code, just hit the green run button on the toolbar at the top (Eclipse automatically compiles the code for you, so you don't have to worry about that).

==Switching Branches==
If you need to run code from another branch or tag, please see [[Switching Branches]].

==Viewing Source and Running From Trunk==
By default all of the rifidi plugins you are running in eclipse are pre-compiled, binary plugins contained in the <code>org.rifidi.binary</code> folder. If you want to view or edit the source for a particular plugin, you will need to check out the plugin from the trunk. Once it is checked out make sure to edit your run configuration so that the application will use the plugin from the workspace and not from the target platform.

For example, suppose I want to view the source for the Alien reader plugin. I need to follow the steps above to check out and run rifidi emulator. In addition, I need to check out the <code>org.rifidi.emulator.readers.alien</code> plugin. This is the code for the alien reader. In addition, I need to edit the run configuration to make sure that my workspace alien reader plugin is being used instead of the target platform alien reader plugin.

=Reporting Bugs=

To report bugs, please use the forum at

http://forums.rifidi.org

or drop by our IRC channel:

<nowiki>#rifidi on irc.freenode.org.</nowiki>

You can also visit us online at http://www.rifidi.org

Rifidi roadmap

2011-10-13T07:33:42Z

Seoagent: /* Current State */

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 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 [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 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 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-13T07:32:59Z

Seoagent: /* Solution through Service Oriented Architecture */

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 [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 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 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-13T07:32:28Z

Seoagent: /* Steps to Complete */

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://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-13T07:32:04Z

Seoagent: /* Steps to Complete */

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://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 products [http://startutor.sgtuition centre]
.
# 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-13T07:30:40Z

Seoagent: /* Rifidi As Single Application */

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://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 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