The Commissioning Reusable Component records the commissioning
of tags, optionally to assets, in the back-end system.
This Reusable Component indicates to the system that the tags are
in use, possibly applied to assets, and ready to be observed by the
sensor network. In order to validate that a tag or group of tags has
been commissioned, call the Validation
Reusable Component, which returns a value of false if any tags
are not currently commissioned. Tags that will be destroyed or no
longer used can be decommissioned by calling the Decommissioning Reusable Component.
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. Commissioning agent propertiesName |
Description |
PID |
Agent properties |
CommissioningAgent |
RUC Commissioning Agent |
com.ibm.premises.reusable.commissioning.CommissioningAgent |
- ruc.targetBackend=ruc.epcis
- commission.output.success=rucresponse/commissioning/commission/success
- commission.output.failure=rucresponse/commissioning/commission/failure
|
WebSphere Application Server configuration
Table 2. Activation specification valuesName |
JNDI name |
Destination type |
Destination JNDI name |
Message selector |
Bus name |
CommissioningRUCAS |
eis/CommissioningRUCAS |
Topic |
jms/ibmse |
ibmse LIKE ‘rucaction/commissioning/%’ OR ibmse
LIKE ‘%/rucaction/commissioning/%’ |
ibmsensorevent |
Methods
- commissionEvent (ISensorEvent IBMSE)
- commission (String IBMSE_XML) (Exposed as Web
service)
- commissionMap (Map IBMSE_Payload_Attrs)
Using the Commissioning Reusable Component
To
invoke the Commissioning 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:
- CommissioningRUCConstants.TAG_KEY_INOUT
- CommissioningRUCConstants.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.
- commission: profileid/rucaction/commissioning
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.