A P P E N D I X B |
RFID Event Manager Component Reference |
This appendix describes the properties of the RFID Event Manager components included with the RFID Software. The following tables list the properties with a description and the valid values. Refer to the property descriptions and values to determine the specific settings for your RFID system. The components are used to create RFID Event Manager roles as described in Chapter 2. See To Define RFID Event Manager Roles.
This component creates a union of EPCs that are discovered over the number of specified n cycles. If an EPC was discovered in cycle < n, it is reported. If an EPC has not been viewed in more than the last n cycles, it is not reported. This component is necessary because the RFID readers do not report tags with 100% accuracy.
This component reports RFID tags leaving and entering the radio frequency fields. For example, on a reader, if at time T1, two EPCs were discovered, then two TagsIn events are reported. If at time T2, one of the EPCs disappeared, then a TagsOut event is reported.
Defines a set of standard logging levels that can be used to control logging output. |
||
Specifies whether to use recorded events from the previous run. |
||
This component performs a pass filter on the value of the RFID tag EPC values. Those EPC values that match the specified EPC pattern are passed on to listeners, while others are not.
Defines a set of standard logging levels that can be used to control logging output. |
||
The BandPass filter is used to select a subset of events that match the specified event source's identity. If an event matches, the Event object is passed to the listeners of the filter, otherwise the Event object is dropped.
An event source identity matches if any of the following conditions are true:
Defines a set of standard logging levels that can be used to control logging output. Possible values are: |
|
An identity URI pattern used for matching. See TABLE B-3 for examples. |
|
An EPC identifier URI or a String for the matching ID. If EPC is an identifier URI, then the match is successful only if the event's source is an identifires that matches the value of this EPC property. If the EPC property is not an identifier URI, then it is treated as a String and the event's source must be a String that matches the EPC value |
This component provides a general connector for the RFID Event Manager and writes PML core to an output file.
This component provides a connector that writes PML core to an HTTP connection.
Defines a set of standard logging levels that can be used to control logging output. Possible values are: |
|
This component provides a connector that sends PML core events using a JMS Message.
The NullConnector filter consumes events and does nothing with them. The primary purpose of this connector is to terminate processing of the the event chain if no external processing is required.
Defines a set of standard logging levels that can be used to control logging output. Possible values in addition to ALL are: |
This component creates a socket connection and starts writing PML core to the connection.
Defines a set of standard logging levels that can be used to control logging output. Possible values are: |
|
This component creates a server socket and, when the socket connection is accepted, starts writing PML to the connection.
Defines a set of standard logging levels that can be used to control logging output. Possible values are: |
|
See Architecture Overview of the RFID Software Plug-In for SAP AII.
The EPCGui connector is a graphical user interface (GUI) that displays RFID tags and the number of consecutive times the tags have been sensed by a reader. The tags change colors from red to yellow to green to indicate the number of times they have been viewed.
This GUI runs inside the same Java virtual machine (Java VM) as the rest of the Execution Agent. To display the GUI on a different system, the shell that launched the Execution Agent must be remotely displayed.
To avoid this limitation, use the RemoteEventProducer connector, which posts events to the TagViewer that can run independently from the Execution Agent.
The EPCGui is useful for debugging. Use the combination of a RemoteEventProducer and TagViewer in a production environment. The system automatically creates a RemoteEventProducer connector for every adapter. This enables the TagViewer to receive nonfiltered tags detected by the reader. If you want to see only filtered tags, then you need to attach a RemoteEventProducer connector to the output of the filter. Then use the TagViewer to see the filtered tags.
Defines a set of standard logging levels that can be used to control logging output. Possible values are: |
|
This component, the remote event producer is a general connector to produce Remote Event objects. This class does not implement guranteed event delivery. If there are no registered consumers of the generated events, the events are lost.
Defines a set of standard logging levels that can be used to control logging output. Possible values are: Also see the java.util.logging.Level and LogLevel property description in TABLE 2-4. |
|
Integer identifier for the event. The consumer must specify the same EventID in order to discover the events. |
|
If true, then use the RoundRobin dispatcher. If false, then dispatch to all registered listeners. |
|
Maximum number of times trying to fire an event with no listeners registered before an exception is thrown The default = 25. |
The EpcisJms connector sends events from the RFID Event Manager to the RFID Information Server using the Java Message Service (JMS) protocol. This connecter populates the CURRENT_OBSERVATION table and the OBSERVATION_LOG table in the RFID Information Server database. Also see Configuring the RFID Event Manager to Use an EpcisJms Connector.
Defines a set of standard logging levels that can be used to control logging output. Possible values are: Also see java.util.logging.Level and LogLevel property descriptions in TABLE 2-4. |
|
Specifies the URL for the RFID Information Server. The URL is of the form: http://hostname:portnumber/epcis/service where hostname is the name of the machine where you installed your RFID Information Server and the portnumber is your HTTP port. |
|
(Optional) Specifies the host name of the HTTP proxy server. |
|
(Optional) Specifies the port number for the HTTP proxy server. |
|
(Required) Specifies the delivery method. Value must be one of the following: |
|
(Optional) Only used if the UseJms property is true or topic. Specifies the topic name for JMS. |
|
(Optional) Only used if the UseJms property is queue. Specifies the queue name for JMS. |
|
(Optional) Only use if the UseJms property is true, topic, or queue. Specifies the Java Naming and Directory Interface (JNDI) name of the connection factory. When UseJms property is true or topic , this property is TopicConnectionFactory When UseJms property is queue, this property is QueueConnectionFactory. |
|
(Optional) Specifies the class name of the initial context factory. See javax.naming.InitialContext for more information. |
|
(Optional) Specifies the provider URL property used by the InitialContext specified by the java.naming.factory.initial property. |
|
(Optional) Specifies the authentication mechanism to be used. Values can be one of the following: |
The EpcisHttp connector sends events from the RFID Event Manager to the RFID Information Server using the HTTP protocol. This connecter populates the CURRENT_OBSERVATION table and the OBSERVATION_LOG table in the RFID Information Server database. Also see Configuring the RFID Event Manager to Use an EpcisHttp Connector.
Defines a set of standard logging levels that can be used to control logging output. Possible values are: Also see the java.util.logging.Level and LogLevel property descriptions in TABLE 2-4. |
|
Specifies the URL for the RFID Information Server. The URL is of the form: http://hostname:portnumber/epcis/service |
|
(Optional) Specifies the port number for the HTTP proxy server |
|
Specifies the delivery method. The value must be one of the following: |
|
(Optional) Specifies the class name of the initial context factory. See javax.naming.InitialContext for more information. |
|
(Optional) Specifies the provider URL property used by the InitialContext specified by the java.naming.factory.initial property. |
|
(Optional) Specifies the authentication mechanism to be used. Values can be one of the following: |
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.