Sensormatic View Manager 96 Console Przewodnik Instalacji Pobierz pdf (Strona 19)

Chapter 2 Configuring the RFID Event Manager 19

The RFID Configuration Manager consists of a configuration service and a user

interface to the service. To begin using the RFID Configuration Manager, it is

necessary to understand the concepts of device profiles, RFID Event Manager

components, roles, configuration objects, and devices.

■ Device profiles – A device profile provides the fully qualified description of a

given RFID reader or other device (such as a printer or sensor) model and its

properties. The device profile provides a sensor input point to the RFID system.

Each model from a hardware vendor has a unique profile that describes it. For

example, the Alien ALR-9780 profile defines that its reader has a maximum of

four antennas, includes an

antennaSequence property to define the order in

which each antenna is probed, and includes a username and a password

property for communication with the device, and so on. Default values are

provided for each device profile, but it is in the device that the values are actually

used.

■ Event Manager components – A component is the basic building block for the

RFID system. All components have inputs and outputs. You can connect the

output of one component to the input of another component to create a

processing chain. Two types of components are currently used by Sun’s RFID

Software:

■ Filters – A filter takes inputs and transforms them, according to an algorithmic

process description, into an output.

■ Connectors – A connector provides a routing point from the process flow to an

external or internal point. Examples of connectors are a Java Message Service

(JMS) connector and a and file connector. A JMS connector places data onto a

JMS queue. A file connector stores data into a file.

See “RFID Event Manager Component Overview” on page 53 for more details on

the components provided with the RFID Software.

■ Event Manager roles – A role is a combination of components providing a

functional capability within the RFID architecture. By themselves, roles are not

functional, as they lack the ability to read data from the RFID system. For

example, a role might represent a dock door, an assembly line station, or a smart

shelf. A role consists of a chain of filters and connectors with a designated data

input point. The data input point defines the RFID Event Manager component

that initially receives and processes the tag event data from the RFID devices. The

role specification replaces a large segment of the contents of the

RfidConfig.xml configuration file.

■ Devices – A device is a concrete physical instance of a particular profile. Multiple

devices can be associated with a specific profile. These devices may or may not be

identical.

■ Configuration objects – A configuration object defines an actual distributed,

active RFID data sensor that provides a RFID reader function. The configuration

object is generally a role that receives input from multiple devices, each of which

belongs to a specific profile. A configuration object associates a set of one or more

physical devices and its respective device profiles to a role. For example, a

1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 191 192

Komentarze do niniejszej Instrukcji

Brak uwag

Sensormatic View Manager 96 Console Przewodnik Instalacji Strona 19

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Systemy kontroli dostępu bezpieczeństwa Sensormatic View Manager 96 Console