WebSphere brand IBM WebSphere Sensor Events, Version 6.2

System agent

The System agent controls the configuration settings for WebSphere® Sensor Events components.

When you add or modify a property for this agent, you should restart WebSphere Application Server. After you restart WebSphere Application Server, there is a 60 second delay before the updates to this agent are available to the system.

Properties

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.

Table 1. System agent properties
Property Description
autoid.core.savantid The EPCGlobal, Inc Savant ID.
cache.refresh.interval

This internal cache is used by WebSphere Sensor Events for the fast retrieval of all WebSphere Sensor Events topology definitions and agent property values, including the properties of the System agent and all of the Reusable Components.

Note: This property is configurable for time delays at startup and after updates. The default value is 60 seconds. Be aware of this delay because if an application tries to query the agent property information within that first minute, it cannot be successfully retrieved.
com.ibm.premises.eventmonitor.TTL This is the length of time in milliseconds that an event lives in the cache. The default is 600000 milliseconds, which is 10 minutes.
com.ibm.premises.eventmonitor.max.queue.size This is the maximum number of events kept in the cache. The default value is 100.
com.ibm.premises.eventmonitor.on This property is used to turn event monitor caching on or off. It is independent of the EventMonitorAS JMS activation specification message selector, which only defines which messages are sent to the event monitor. The possible values are true or false, and the default value is false.
com.ibm.premises.report.location Defines the location where the WebSphere Sensor Events BIRT reports are stored.
com.ibm.rfid.applping.shortcut Defines whether the application ping message is returned by EBO or WebSphere Sensor Events.
com.ibm.rfid.dms.server.bundlerepository The DMS bundle repository directory.
com.ibm.rfid.dms.server.hostname The host name of the DMS bundle repository.
com.ibm.rfid.location.external.format Indicates how locations are reported to enterprise systems.
com.ibm.rfid.location.external.format.delimiter The delimiter to use between nodes in a fully qualified name. Used in conjunction with com.ibm.rfid.location.external.format.
com.ibm.rfid.premises.edgeconfig.delete.filter Indicates the filter value to use in the WebSphere Sensor Events Edge configuration xml in <request type="delete"> <configuration filter="<property value>"/> </request>.
com.ibm.rfid.premises.sysman.logging.resources Specifies the name of the ResourceBundle to use for internationalizing messages going to the WebSphere Sensor Events custom log files. These files consist of the alert and heartbeat logs.
com.ibm.sensorevent.converter Defines the class used to convert between XML and events.
com.ibm.sensorevent.externalize.header.properties.inbound This property can be set to true or false. It tells the gateway if it should open the SensorEvent and copy properties from the SensorEvent header and set them as JMS properties on the JMS message envelope. Setting this property to true could impact performance; however, it would allow task agents or Reusable Components to set message selectors on any property in the SensorEvent header, giving these agents another level of filtering that is not ordinarily available.
com.ibm.sensorevent.externalize.header.properties.outbound This property can be set to true or false. It tells the JMS output channel if it should open the SensorEvent and copy properties from the SensorEvent header and set them as JMS properties on the JMS message envelope. Setting this property to true could impact performance; however, it would allow external applications to set message selectors on any property in the SensorEvent header, giving these external applications another level of filtering that is not ordinarily available.
com.ibm.sensorevent.persistence.db Directs the WebSphere Sensor Events to persist all events to the database. If this property is set to true, all events are saved to the database. If this property is set to any value other than true, all events are not saved to the database.
com.ibm.sensorevent.persistence.epcis Directs the WebSphere Sensor Events to persist all events to EPCIS. If this property is set to true, all events are sent to EPCIS. If this property is set to any value other than true, all events are not sent to EPCIS.

Library | Support | Terms of use

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