WebSphere brand IBM WebSphere Sensor Events, Version 6.2

Reporting

The Reporting Reusable Component queries the back-end system for tag and location history based on previously observed events.

The output attributes for the Reporting Reusable Component are an array of maps. Each map includes name-value pairs pulled from the recorded observation events for the specified tag or location. These generally include tag, location, timestamp, eventId, eventType, and any metadata.

If the tag or location filter is left blank, all recorded observation events will be returned.

In order to reduce the massive amount of data that could be returned from a call to the Reporting Reusable Component, the startTime and endTime parameters are allowed. Either or both of these can be null or empty if time filtering is not desired.

The filter eventCountLimit : number is supported as an optional agent property. Use this property to limit the total size of the array of maps returned by the queries to number.

WebSphere Sensor Events configuration

Table 1. Reporting agent properties
Name Description PID Agent properties
ReportingAgent RUC Reporting Agent com.ibm.premises.reusable.reporting.ReportingAgent
  • ruc.targetBackend=ruc.epcis
  • bytag.output.success=rucresponse/reporting/bytag/success
  • bytag.output.failure=rucresponse/reporting/bytag/failure
  • byloc.output.success=rucresponse/reporting/byloc/success
  • byloc.output.failure=rucresponse/reporting/byloc/failure

WebSphere Application Server configuration

See Configuring the messaging interface for the WebSphere® Application Server configuration details.

Methods

Using the Reporting Reusable Component

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.

To invoke the bytag action, which corresponds to the getTagLocationHistory method, the payload must include:

Generic payload created from a map can also be used. It must include either of the following:

Note: TAG_KEY_INOUT takes a String value. TAGLIST_KEY_INOUT takes a value of java.util.List populated with Strings.

To invoke the byloc action, which corresponds to the getLocationTagHistory method, either the payload or payloadMetadata must include:

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 ObjectEventConstants.RUCMDB_RESULT_KEY_OUT with a counter appended for every event map returned. For example:


Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2009. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.