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

Validation

The Validation Reusable Component queries the back-end system to validate whether or not the tags passed to the validate method are currently commissioned. A list of tag EPCs are extracted from the input event and validated against the commissioning history. Non-commissioned tags mean that the tag has never been commissioned or the tag has more recently been decommissioned.

If any tags are not currently commissioned, the validate call returns false. The Validation Reusable Component does not report if multiple tags are passed, specify which tags are not commissioned, or provide details about if or when tags has been decommissioned.

If the call returns true, all tags passed are ready to be observed by the sensor network.

WebSphere Premises Server configuration

Table 1. Validation Properties
Name Description PID Agent properties
ValidationAgent RUC Validation Agent com.ibm.premises.reusable.validation.ValidationAgent
  • ruc.targetBackend=ruc.epcis
  • validate.output.success=rucresponse/validation/validate/success
  • validate.output.failure=rucresponse/validation/validate/failure

WebSphere Application Server configuration

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

Methods

Using the Validation Reusable Component

To invoke the Validation 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:
  • ValidationRUCConstants.TAG_KEY_INOUT
  • ValidationRUCConstants.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.
  • validate: profileid/rucaction/validation
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. The payload includes:
  • validate: ValidationRUCConstants.VAL_RUC_RESULTBOOL_KEY_OUT

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.