WebSphere brand IBM WebSphere Premises Server 6.1 Feature Pack for Sensor Event Services

Observation

The Observation Reusable Component records observed events in the back-end system. This is the simplest recording of sensor events to a back-end repository. After being observed, events can be queried using the Locating or Reporting Reusable Components.

All IBM® Sensor Event data and payload metadata are maintained in a call to the EPCIS Connector. For more information, see Working with the EPCIS Connector sample application.

WebSphere Premises Server configuration

Table 1. Observation agent properties
Name Description PID Agent properties
ObservationAgent RUC Observation Agent com.ibm.premises.reusable.observation.ObservationAgent
  • ruc.targetBackend=ruc.epcis
  • observe.output.success=rucresponse/observation/observe/success
  • observe.output.failure=rucresponse/observation/observe/failure

WebSphere Application Server configuration

Table 2. Activation specification values
Name JNDI name Destination type Destination JNDI name Message selector Bus name
ObservationRUCAS eis/ObservationRUCAS Topic jms/ibmse ibmse LIKE ‘rucaction/observation/%’ OR ibmse LIKE ‘%/rucaction/observation/%’ ibmsensorevent

Methods

Using the Observation Reusable Component

To invoke the Observation Reusable Component using IBM Sensor Events or XML, the payload must include:
  • PassiveRFIDTagRead
  • PassiveRFIDAggregatedTagRead
Generic payload created from a map can also be used. It must include either of the following:
  • ObservationRUCConstants.TAG_KEY_INOUT
  • ObservationRUCConstants.TAGLIST_KEY_INOUT
Note: TAG_KEY_INOUT takes a String value. TAGLIST_KEY_INOUT takes a value of java.util.List populated with Strings.
To publish to Reusable Components MDBs, set the following values for the JMS topic and eventType. For single-action Reusable Components, the topic is only checked in the message selector.
  • observe: profileid/rucaction/observation
The JMS topic and eventType for the MDB output from the Reusable Component comes from the agent properties. Default output topics for success and failure for each action are shown in Table 1. There is no payload.

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.