This section describes how to create and
manage configuration groups for
controllers, locations, and devices within your WebSphere® Sensor Events infrastructure
using the WebSphere Sensor Events Administrative Console and Data Capture and Delivery.
Use the WebSphere Sensor Events Administrative Console to
define and manage configuration groups that
define the infrastructure components of the product. Configuration
groups help you manage controllers, locations, agents, and devices
(Bartender and Loftware logical printers, readers, and simulated reader)
as part of a group instead of individually.
Configuration groups
WebSphere Sensor Events offers
three
configuration group types: location type, controller
type, and device type. Each
configuration group type in
the product defines a set of one or more agents with their configurations
and a set of zero or more
configuration group metadata
properties. After you define a
configuration group type,
you assign agents and their configurations to it and then define the
metadata to store with that
configuration group.
Configuration group and category metadata display on the
WebSphere Sensor Events Administrative Console; however,
you define and manage the metadata through the XML configuration file
that you import.
Note: The
WebSphere Sensor Events imports
metadata files based on the Metatype Service Specification as defined
within the OSGi Service Platform - Service Compendium, Release 4,
August 2005 that is distributed by the OSGi Foundation. For additional
information, go to
www.osgi.org.
The
product, by default, comes with several preset location configuration
groups. One location configuration group is
called Enhanced Dock Door Receiving. This location configuration group type contains
all the agents that are part of the enhanced dock door receiving usage
scenario along with the correct agent configurations. What this means
is that an agent can exist in the system with different configurations
for different configuration groups.
In addition, you can associate each configuration group with
a category. For example, you can create a device configuration group called Sirit.
You then assign this configuration group,
Sirit, to the category reader. Each category also has its own
set of metadata properties.
You use the WebSphere Sensor Events Administrative Console to
implement and manage configuration groups.
You can also import an XML document into the WebSphere Sensor Events. The
XML document enables you to create, update, and delete various product configuration groups and configuration group types.
For
additional information about device, location, and controller
configuration groups,
refer to the topics below:
Configuring using the console or an XML file
You
can perform the following functions using either the
WebSphere Sensor Events Administrative Console or
the XML configuration file:
- Create, edit, and delete new location, controller, and device configuration groups.
- Create, edit, and delete locations, controllers, and devices (for
readers, logical printers, and simulated readers).
- Assign locations to location configuration groups.
- Assign devices to device configuration groups.
- Assign controllers to controller configuration groups.
- Create, edit, and delete agents and agent properties for Data Capture and Delivery.
- Assign agents and their configurations to a configuration group.
You can perform the following functions only using the
imported configuration XML file:
- Create new categories, and update and delete categories and category
metadata.
- Create, update, and delete configuration group metadata.