The WBE Reusable Component allows WebSphere® Premises Server application
developers to forward tag read events to WebSphere Business Events to be
processed by the rules engine. In WebSphere Business Events, Event
Flows and Interaction Sets define the rules that are processed when
the tag read enters WebSphere Business Events.
WebSphere Business Events must
be installed in order to use the WBE Reusable Component. See Installing WebSphere Business Events for
information.
When defining Event Flows and Interaction Sets, use the files found
in the IBM_RFID_HOME\install\wbe directory.
The PremisesProject.xml file in that directory
contains the WebSphere Business Events definition
for the WebSphere Premises Server TagRead
events, Event objects, Intermediate objects, and sample Actions.
WebSphere Premises Server configuration
Table 1. WBE agent propertiesName |
Description |
PID |
Agent properties |
WBEAgent |
RUC WBE Agent |
com.ibm.premises.reusable.wbe.WBEAgent |
- wbe.output.success=rucresponse/wbe/decommission/success
- wbe.output.failure=rucresponse/wbe/decommission/failure
- wbeport=port_number
|
WebSphere Application Server configuration
Table 2. Activation specification valuesName |
JNDI name |
Destination type |
Destination JNDI name |
Message selector |
Bus name |
WBERUCAS |
eis/WBERUCAS |
Topic |
jms/ibmse |
ibmse LIKE ‘rucaction/wbe/%’ OR ibmse LIKE ‘%/rucaction/wbe/%’ |
ibmsensorevent |
Methods
- publishEventToWBE (ISensorEvent IBMSE)
- publishToWBE (String IBMSE_XML) (Exposed as
Web service)
- publishMapToWBE (Map IBMSE_Payload_Attrs)
Using the WBE Reusable Component
To invoke
the WBE 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:
- WBERUCConstants.TAG_KEY_INOUT
- WBERUCConstants.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 multi-action Reusable Components,
the topic is checked in the message selector and in the MDB code.
- wbe: profileid/rucaction/wbe
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.