RFID Software Administration Guide Table Of ContentsPrevious ChapterNoNextNoIndex


A P P E N D I X  C

 

RFID Configuration File

This appendix illustrates sample configuration files for the semantics of an Execution Agent. The semantics are contained in an XML configuration file for each Execution Agent. It may be necessary to create and edit these configuration files manually. By default, the system ships configured to execute with one Execution Agent.

Sample Default RFID Configuration Files

The Execution Agent configuration syntax is illustrated below:


FIGURE C-1 Configuration File Hierarchy


The name and value properties used are case sensitive. For instance, a value of EPC is treated differently from Epc.

Properties appropriate to each of the configurable entities (adapters, filters and loggers) are shown in other appendices in this book.


TABLE C-2 Sample xml Code for a Filter 
<ems:filter>

   <ems:name>RfidSmoother</ems:name>

   <ems:classname>com.sun.autoid.filter.Smoothing</ems:classname>

      <ems:properties>

         <ems:property>LogLevel</ems:property>

         <ems:value>CONFIG</ems:value>

      </ems:properties>

      <ems:properties>

         <ems:property>MaxCycles</ems:property>

         <ems:value>5</ems:value>

      </ems:properties>

      <ems:properties>

         <ems:property>MaxPersistTime</ems:property>

         <ems:value>5000</ems:value>

      </ems:properties>

      <ems:outputs>

         <ems:output>RfidDelta</ems:output>

      </ems:outputs>

</ems:filter>

ALE Web Services Configuration Files

In ALE there is a concept of physical reader and logical reader. A logical reader can be comprised of one or more physical readers. For a reader to participate in the ALE implementation, its configuration must include an REProducer that defines the physical reader and logical reader name. The name of the physical reader defined in the reader configuration file, RfidConfig.xml, must match the name for the service defined in the readers.xml file contained in /etc/opt/sun/rfidem. A sample configuration file, RfidConfig.xml, to support this is listed in CODE EXAMPLE C-1 and a sample readers.xml is listed in CODE EXAMPLE C-2.


CODE EXAMPLE C-1 Sample ALE RfidConfig.xml

<ems:adapter>

<ems:name>Matrics Reader</ems:name> <ems:classname>com.sun.autoid.adapter.matrics.MatricsReaderAdapter

</ems:classname>

<ems:outputs>

<ems:output>ALE</ems:output>

</ems:outputs>

</ems:adapter>

<ems:filter>

<ems:name>ALE</ems:name>

<ems:classname>com.sun.autoid.ale.AleEventFilter</ems:classname>

<ems:properties>

<ems:property>LogLevel</ems:property>

<ems:value>CONFIG</ems:value>

</ems:properties>

<ems:properties>

<ems:property>startTrigger</ems:property>

<ems:value>urn:epc:pat:gid-96:*.*.*</ems:value>

</ems:properties>

<ems:properties>

<ems:property>duration</ems:property>

<ems:value>60000</ems:value>

</ems:properties>

<ems:outputs>

<ems:output>ALEReport</ems:output>

</ems:outputs>

</ems:filter>

<ems:filter>

<ems:name>ALEReport</ems:name>

<ems:classname>com.sun.autoid.ale.AleEventReportFilter</ems:classname>

<ems:properties>

<ems:property>LogLevel</ems:property>

<ems:value>CONFIG</ems:value>

</ems:properties>

<ems:properties>

<ems:property>ReportName</ems:property>

<ems:value>report1</ems:value>

</ems:properties>

<ems:properties>

<ems:property>ReportSet</ems:property>

<ems:value>CURRENT</ems:value>

</ems:properties>

<ems:properties>

<ems:property>OutputSpecIncludeList</ems:property>

<ems:value>true</ems:value>

</ems:properties>

<ems:outputs>

<ems:output>ALEOutput</ems:output>

<ems:output>RfidEventProducer</ems:output>

</ems:outputs>

</ems:filter>

<ems:logger>

<ems:name>ALEOutput</ems:name>

<ems:classname>com.sun.autoid.ale.AleJMSReportLogger</ems:classname>

<ems:properties>

<ems:property>LogLevel</ems:property>

<ems:value>CONFIG</ems:value>

</ems:properties>

<ems:properties>

<ems:property>NotificationURI</ems:property> <ems:value>jms:/topic/com.sun.jndi.fscontext.RefFSContextFactory/epcis

</ems:value>

</ems:properties>

</ems:logger>

<ems:logger>

<ems:name>RfidEventProducer</ems:name>

<ems:classname>com.sun.autoid.logger.REProducer</ems:classname>

<ems:properties>

<ems:property>LogLevel</ems:property>

<ems:value>CONFIG</ems:value>

</ems:properties>

<ems:properties>

<ems:property>EventID</ems:property>

<ems:value>12551</ems:value>

</ems:properties>

<ems:properties>

<ems:property>LogicalReader</ems:property>

<ems:value>Dock Door 1</ems:value>

</ems:properties>

<!-- NOTE the ServiceBean name must match the Physical Reader defined in the REProducer in he associated RfidConfig.xml for ALE to work properly -->

 

<ems:properties>

<ems:property>PhysicalReader</ems:property>

<ems:value>Reader</ems:value>

</ems:properties>

</ems:logger>

 



CODE EXAMPLE C-2 Sample readers.xml File

<opstring>

<OperationalString Name="Readers"> 

 

<!-- NOTE the ServiceBean name must match the Physical Reader defined in the REProducer in the associated RfidConfig.xml for ALE to work properly --> 

 

<ServiceBean Name="Reader" MatchOnName="yes">

 


To fully understand the ALEEventFilter it is necessary to understand the ALE specification. An ECSpec describes an event cycle and one or more reports that are to be generated from it. It contains a list of logical Readers whose read cycles are to be included in the event cycle, a specification of how the boundaries of event cycles are to be determined, and a list of specifications each of which describes a report to be generated from this event cycle. A sample of an ECSpec is listed in CODE EXAMPLE C-3.


CODE EXAMPLE C-3 Sample ECSpec File

<?xml version="1.0" encoding="UTF-8"?>

 

<ECSpec xmlns="urn:epcglobal:ale:xsd:1"

includeSpecInReports="true"

creationDate="2005-02-07T13:42:40.790-05:00"

schemaVersion="1.0"> 

 

<logicalReaders xmlns="">

<logicalReader>Reader</logicalReader>

</logicalReaders> 

 

<boundarySpec xmlns="">

<startTrigger>http://localhost/start</startTrigger>

<duration>2000</duration>

<stableSetInterval>0</stableSetInterval>

</boundarySpec> 

 

<reportSpecs xmlns="">

<reportSpec reportIfEmpty="false"

reportName="ReporT"

reportOnlyOnChange="false">

<reportSet set="CURRENT"/>

<output includeCount="false" includeList="true"/>

</reportSpec>

</reportSpecs>

</ECSpec> 

 



  RFID Software Administration Guide 819-1697-10 Table Of ContentsPrevious ChapterNoNextNoIndex


Copyright © 2004, Sun Microsystems, Inc. All Rights Reserved.