The EPCIS Connector agent converts an ISensorEvent (tag reads, aggregated tag reads, or generic event) into EPCIS XML events. The generated XML is augmented with additional information based on name-value pairs
There are common properties shared by all Reusable Component agent. For more details on these properties, see the WebSphere® Sensor Events Toolkit documentation.
Property | Description |
---|---|
action-name.output.success | The topic to use for a response from the message-driven bean (MDB) when an action is successful. |
action-name.output.failure | The topic to use a response from the MDB when an action is unsuccessful. |
ruc.targetBackend | This property defines the target interface or enterprise application that contains the Reusable Component implementation logic, such as ruc.epcis, ruc.wse, ruc.its, ruc.db, or ruc.custom. |
ruc.targetBackendJNDI | This property is used when you have a custom back-end implementation (ruc.custom). Use this property to point to the new back-end EJB. |
The possible values for action-name for the EPCIS Connector agent properties are:
Property | Description |
---|---|
include.location.context | This property determines whether to include location context (metadata) in the agent event that is stored in the sage.objectinstancemetadata table when the event is generated. The possible values are true to include, or false to exclude. The default value is false. |
publish.outbound.topic | The name of the event template defined in the WebSphere Sensor Events server that will publish the event. |
publish.outbound.parameter.key | The property key used when building the outbound topic. It is added to the publish.outbound.topic value. |