The delete filter for Data Capture and Delivery is an LDAP
filter that is used to clear configurations from the Data Capture and Delivery device.
The delete filter must be set correctly so that duplicate configurations
are not stored in ConfigAdmin, causing duplicate agents that can compete
for the same resources. For example, if a reader's configuration is
not deleted, then when the Data Capture and Delivery controller
starts it will load a second copy of the reader configuration, creating
a second agent. Both agents will try to open the same port on the
same reader at the same IP address.
To view the delete filter configuration settings in the SystemAgent,
navigate to .
Delete filter configuration settings
The setting for the delete filter is configurable
in the SystemAgent.
- The filter that is installed by default deletes all configurations except the
EdgeConfigAgent configuration. This configuration is required because
it is for the agent that controls the configuration process).
(!(service.pid=com.ibm.rfid.edge.config))
Notes: - The edge.config agent configuration is the only one that must
be saved. If you are storing any additional settings in ConfigAdmin
that should not be deleted, modify this filter or use a different
one.
- This filter will delete the configuration of the Bundle Loader
agent. This means that on subsequent starts, after the initial startup
or load, the Bundle Loader agent will attempt to download its specified
bundle list again, even if it has not changed, since any previous
knowledge of its load state has been deleted. The Bundle Loader agent
looks at each entry in the bundle list, logs that it is loading the
bundle, notices that the bundle's URL has already been loaded, and
therefore, does not actually download it. This means that a small
amount of extra network activity occurs to get the bundle list, but
no bundles are actually transferred, assuming they were downloaded
previously. To avoid this small amount of network activity, use the
next filter option.
- To delete all configurations except for the bundle.loader and
edge.config, and therefore to delete configurations for any additional
third party agents, such as readers, set the filter value to this:
(!(|(service.pid=com.ibm.rfid.bundle.loader)
(service.pid=com.ibm.rfid.edge.config)))
Note: With this
option, the Bundle Loader agent remembers which bundle lists it has
successfully loaded. If the set of bundle list URLs has not changed,
no bundles will be downloaded.
- To delete only the agent configurations (except for bundle.loader
and edge.config) and to leave all other configurations in ConfigAdmin,
set the filter value to this:
(&(service.pid=com.ibm.rfid*)
(!(|(service.pid=com.ibm.rfid.bundle.loader)(service.pid=com.ibm.rfid.edge.config))))
- To delete only agent configurations (except for bundle.loader
and edge.config) and also to delete all configurations for com.sirit*, com.intermec*, com.motorola.symbol*,
and service.pid=com.alien*, set the filter value
to this:
(|(|(|(|(|(service.pid=com.sirit*)
(service.pid=com.intermec*))(service.pid=com.motorola.symbol*))(service.pid=com.alien*))
(service.pid=org.eclipse.soda.dk*))(&(service.pid=com.ibm.rfid*)
(!(|(service.pid=com.ibm.rfid.bundle.loader)(service.pid=com.ibm.rfid.edge.config)))))
- To delete every configuration, set the filter value to this:
(service.pid=*)
Note: This value is not recommended
for a standard WebSphere® Sensor Events installation
and Data Capture and Delivery clients.