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

Decommissioning

The Decommissioning Reusable Component records the tags that will be destroyed or no longer used in the back-end system.

This Reusable Component indicates to the system that the tags are no longer in use and not ready to be observed by the sensor network. In order to validate that tags have been decommissioned, call the Validation Reusable Component, which returns a value of false if any tags are not currently commissioned.

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. Decommissioning agent properties
Name Description PID Agent properties
DecommissioningAgent RUC Decommissioning Agent com.ibm.premises.reusable.Ddecommissioning.DecommissioningAgent
  • ruc.targetBackend=ruc.epcis
  • decommission.output.success=rucresponse/decommissioning/decommission/success
  • decommission.output.failure=rucresponse/decommissioning/decommission/failure

WebSphere Application Server configuration

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

Methods

Using the Decommissioning Reusable Component

To invoke the Decommissioning 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:
  • DecommissioningRUCConstants.TAG_KEY_INOUT
  • DecommissioningRUCConstants.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.
  • decommission: profileid/rucaction/decommissioning
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.

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.