WebSphere brand IBM WebSphere Sensor Events, Version 6.2

ALE 1.1 ECReports servlet

The ECReports servlet is installed with WebSphere® Sensor Events and allows ALE 1.1 implementations to send ECReports to the sensor event gateway. The servlet accepts XML as input and converts it into an IBMSensorEvent that is then placed on the SIBus.

ECReports are sent to the servlet using the POST method in the body of the HTTP request that is called by the ALE 1.1 implementation. The corresponding IBMSensorEvents are published by the servlet to the SIBus with the topic ibmse/EDDR/report/TagAggregationReport.

The ECReports servlet can also be used to get ALE events from Data Capture and Delivery to WebSphere Sensor Events ALE.

Notes:

Accessing the servlet

The servlet is installed with WebSphere Sensor Events. To access the servlet, enter the following URL into a browser: http://localhost:9080/ibmse/ECReport.

Recommended usage

The ECReports Servlet receives the ECReports output from an ALE engine. This implies that there is at least one ECSpec defined on that ALE engine, with a subscription using the servlet URL; for example, http://premises_ip_address:9080/ibmse/ECReport. For best results, the following restrictions should apply to any ECSpec being used in conjunction with this servlet:
  • The includeSpecInReports attribute should have a value of true. If the value is set to false, all ECReports that do not include the original ECSpec are ignored.
  • Only one logical reader should be referenced. If more than one logical reader is referenced, only the first in the list is used as part of the generated sensor event. This gives the appearance that all tags within the reports came from the first reader in the list.

    If the value of the logical reader corresponds to a reader or device ID assigned to a location within the topology, or the value does not correspond to a reader ID or a location ID within the topology:

    1. The generated sensor event is published to the SIBus using a topic of ibmse/ALE/report/TagAggregationReport.
    2. The event is persisted to the database.
    3. The following exception shows up in the log file related to the Tag Read Task agent because neither the devices or the locations outside of the topology have an associated alias:
      00000065 KimonoTaskLog E com.ibm.sensorevent.DDR.taskagents.ejb.TagReadTaskAgentBean 
      onIBMSensorEvent TRAS0014I: The following exception was logged 
      com.ibm.rfid.premises.app.access.PremisesAccessException: javax.ejb.ObjectNotFoundException: 
      Single object finder returned 0 objects.
    4. The BIRT report is unavailable.
  • The logical reader should match a leaf location ID, one at the bottom of the tree with a reader assigned to it instead of one that serves as a container for other locations, within the topology. If the location ID used serves as a container for other locations, the generated sensor event is published to the SIBus using a topic of ibmse/ALE/report/TagAggregationReport, and the event is persisted to the database.

Adhering to these restrictions ensures that the tag read information flows through the system with no issues and maximizes the reuse of existing functionality. For example, information is viewable as a BIRT report, which is only generated for locations within the topology. The generated sensor events are persisted to the database and published to the SIBus using a topic of ibmse/profile/report/TagAggregationReport. The value of profile is determined by looking up the location type associated with the logical reader; for example, BDDR for Basic Dock Door Receiving, SDDR for Standard Dock Door Receiving, and EDDR for Enhanced Dock Door Receiving.

The following is an example XML message defining an ECSpec that complies with these restrictions and assumes a default WebSphere Sensor Events location topology:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope 
		xmlns:impl="urn:epcglobal:ale:wsdl:1" 
		xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
		xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
<soapenv:Body>
    <impl:Define>
    	<impl:specName>ECSpecName1</impl:specName>
    	<impl:spec 
    			creationDate="2008-02-19T10:54:06.444-05:00" 
    			schemaVersion="1.1" 
    			xmlns="urn:epcglobal:ale:xsd:1"
			includeSpecInReports="true">
    		<logicalReaders>
        		<logicalReader>P2</logicalReader>
    		</logicalReaders>
    		<boundarySpec>
    			<duration unit="MS">10000</duration>
    		</boundarySpec>
    		<reportSpecs>
        		<reportSpec reportIfEmpty="true" reportName="ReportName1">
            		<reportSet set="CURRENT"/>
            		<output includeTag="true"/>
        		</reportSpec>
    		</reportSpecs>
    	</impl:spec>
    </impl:Define>
  </soapenv:Body>
</soapenv:Envelope>

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.