Configuring the BEA Mobile Tag Read Sample Application
You can configure the BEA Mobile Tag Read sample application by editing the following file: BEA_MOBILE_HOME/samples/tagread/BEAMobileTagRead.config.xml
You can edit the file directly on the mobile device, or copy it to your Windows system for editing and subsequent update back to the mobile device.
The BEAMobileTagRead.config.xml file is a configuration properties file for the BEA Mobile Tag Read sample application. BEA_MOBILE_HOME is the directory in which you installed the BEA Mobile software on the mobile device.
This file is formatted as a .NET application properties XML file, where each line defines a configuration parameter. Lines beginning with <!-- and ending with --> are comments and are ignored by the sample application during processing. The file is self-documenting in that each property or set of properties is described by the comments preceding it.
To enable the changes made to the BEAMobileTagRead.config.xml file, the sample application must be restarted.
Table 8-1 describes the BEAMobileTagRead.config.xml properties that define the reader configuration.
Table 8-1 Reader Property Names/Descriptions in BEAMobileTagRead.config.xml
The reader class name for configured physical reader name (for example, Handheld1).
Once the BEA Mobile Tag Read sample application is running, you can perform the operations described in
Table 8-5 Sample Application Operations
Description. . .
To edit the sample application configuration properties, select Actions EditConfig... to display the Edit Config dialog box. The Edit Config dialog allows you to dynamically configure the following EPCIS capture properties without an application restart:
EPCIS action (ADD, OBSERVE, DELETE)
Read point URIs
Business location URIs
Business step URIs
EPCIS business transactions
These selections are preserved across application restarts.
To initiate a tag read, point the antenna of the mobile device at an RFID tag and pull the trigger. The sample application reads continuously while the trigger is held and stops reading when the trigger is released. After the trigger has been released, the tag read in EPC format is displayed in the main UI and the Tags tile is updated with the tag count.
The status bar displays informational messages pertaining to the performed action.
If the isImmediateSend property in the BEAMobileTagRead.config.xml file is set to false, the tag reads are persisted in the configured persistence store location.
If the isImmediateSend property in the BEAMobileTagRead.config.xml file is set to true, then EPCIS events representing the tag reads are sent immediately to the configured destination URIs.
Clear Displayed Reads
To clear the tag reads displayed on the Select Actions Clear Displayed Readsto clear out the tag reads displayed in the main UI. The main UI is cleared of tag reads and the status bar indicates that the displayed reads were cleared.
Send Persisted Reads
To send all persisted reads, select Actions Send Persisted Reads to send all persisted reads to the configured destination URIs. The Status Bar displays the number of messages successfully sent.
Clear Persisted Reads
To clear persisted reads from the persistence store, select ActionsClear Persisted Reads. The status bar confirms that the persisted reads were cleared
Obtain Version Information
To display application and reader version information, select HelpAbout.
You can now start your own application development, using the BEA WebLogic RFID Edge Mobile SDK APIs. For complete reference information, sample applications, and code walkthroughs, see
Programming with the BEA WebLogic RFID Edge Mobile SDK APIs.