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

Info

The Info Reusable Component queries the back-end system for detailed master data information for tags. It can be considered a more detailed version of the Locating Reusable Component because it returns information from the master data repository in addition to returning the most recently observed event.

The input attributes for the Info Reusable Component are: info.key.itemInfo and info.key.masterData.

This query is supported only when you are using ruc.rfidic as the ruc.targetBackend property value.

WebSphere Premises Server configuration

Table 1. Info agent properties
Name Description PID Agent properties
InfoAgent RUC InfoAgent com.ibm.premises.reusable.info.InfoAgent
  • ruc.targetBackend=ruc.rfidic
  • info.output.success=rucresponse/info/getinfo/success
  • info.output.failure=rucresponse/info/getinfo/failure

WebSphere Application Server configuration

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

Methods

Using the Info Reusable Component

To invoke the Info 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:
  • InfoRUCConstants.TAG_KEY_INOUT
  • InfoRUCConstants.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 value for the JMS topic and eventType. For single-action Reusable Components, the topic is only checked in the message selector.
  • info: profileid/rucaction/info
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 a group with the name InfoRUCConstants.INFO_RUC_RESULTMAPLIST_KEY_OUT with a counter appended for every event map returned. For example:
  • com.ibm.premises.reusable.info.result1 -> Map1
  • com.ibm.premises.reusable.info.result2 -> Map2
  • com.ibm.premises.reusable.info.result3 -> Map3

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.