WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Managing persistence

This topic describes how to configure event persistence.

You can change how tag reads and events persist by modifying values in the SystemAgent.

Note: After modifying the SystemAgent, you must restart the WebSphere Premises Server.

Persisting events to the database

If you want all of your events saved to the database, set the value of the com.ibm.sensorevent.persistence.db property to true in the SystemAgent. If this property is set to any value other than true, all events are not saved to the database. The default value is true.

Persisting events to an EPCIS

If you set the value of com.ibm.sensorevent.persistence.epcis to true, then all events are sent to the EPCIS Connector. If you set the value to false, then the events are not sent to the EPCIS Connector. The default value is false.

For more information on using the EPCIS Connector, refer to the topic on the EPCIS Connector sample application.

Filtering persisted events

About this task

To filter persisted events, administrators can change the message selector value in the PersistenceAS activation specification in the WebSphere Application Server administrative console.

Procedure
  1. Open the WebSphere Application Server administrative console.
  2. Navigate to Resources > JMS > Activation specifications and click PersistenceAS.
  3. Edit the Message selector field to the desired filter value. The default value limits the events persisted to tag read and aggregated tag read events:
    ibmse='RfidInventory/TagReport' OR 
    ibmse='RfidInventory/TagAggregationReport' OR ibmse LIKE
     '%/report/TagReport' OR ibmse LIKE '%/report/TagAggregationReport'

Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.