The Virtual Portal agent bundles two readers to establish a virtual portal that uses a subset of antennas from each reader.
For the properties below, you can enter either strings or variables. If you enter a variable, the value is substituted from the database when the XML configuration file is generated. Refer to Using variables for agent property values for details on what variables can be substituted.
Property | Description |
---|---|
log.level | The level of logging to use with this agent. If the value is empty then the system log level will be used. |
master.reader.activation.expression | The LDAP expression used to activate the tag read on the master reader. |
master.reader.antennas | A comma-delimited list of the antennas on the master reader to apply on the virtual portal. |
master.reader.prefix | The ID of the master reader for the virtual portal. |
portal.id | The portal ID associated with this agent. |
portal.name | The portal name associated with this agent. |
secondary.reader.antennas | A comma-delimited list of the antennas on the secondary reader to apply on the virtual portal. |
secondary.reader.prefix | The ID of the secondary reader for the virtual portal. |
source.id | The source ID for generic events in this agent. |
tracing | Displays trace output. |
virtualportal.eventtype | The event types to assign to the publish topic. |
virtualportal.publish.topic | The publish/subscribe topic to which the virtual portal agent will publish the tag reports. |
virtualportal.sourceid | The source ID to assign to the publish topic. |
The diagram below represents the main concepts for the configuration for virtual portals. First, there is a primary reader with a software stack that is responsible for driving a particular portal, such as the input and the output, turning the readers on and off, and so on. Then, there is a secondary reader, which is only following the state of the primary reader. For example, the secondary reader is turned on at the same time as the primary reader, but has no additional responsibilities. The Portal Controller agent has additional parameters so that it can trigger a second reader through the Control Profile (control bits), and the Virtual Portal agent filters the data coming from two readers and assigns it to the correct portal location based on the antenna.