The Locating Reusable Component queries the back-end system
for the most recent location where a tag has been observed.
The output attributes for the Locating Reusable Component are a
map of name-value pairs pulled from the most recently recorded observation
event for this tag. These generally include tag, location, timestamp,
eventId, eventType, and any metadata.
If the tag to locate is left blank, the most recently recorded
observation event is returned.
WebSphere Premises Server configuration
Table 1. Locating agent propertiesName |
Description |
PID |
Agent properties |
LocatingAgent |
RUC LocatingAgent |
com.ibm.premises.reusable.locating.LocatingAgent |
- ruc.targetBackend=ruc.epcis
- locate.output.success=rucresponse/locating/locate/success
- locate.output.failure=rucresponse/locating/locate/failure
|
WebSphere Application Server configuration
Table 2. Activation specification valuesName |
JNDI name |
Destination type |
Destination JNDI name |
Message selector |
Bus name |
LocatingRUCAS |
eis/LocatingRUCAS |
Topic |
jms/ibmse |
ibmse LIKE ‘rucaction/locating/%’ OR ibmse LIKE
‘%/rucaction/locating/%’ |
ibmsensorevent |
Methods
- (Map) locate(String tag) (Exposed as Web service)
Using the Locating Reusable Component
It
is recommended to invoke the methods using stateless session beans
or a Web Service by passing the following parameters:
- locate
- Locates the most recent location where a tag has been observed
To invoke the Locating 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:
- LocatingRUCConstants.TAG_KEY_INOUT
- LocatingRUCConstants.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.
- locate: profileid/rucaction/locating
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.