Configuring a Simulator

Purpose

This tutorial describes how to configure a Simulator using Oracle Sensor Edge Server.

Time to Complete

Approximately 35 minutes

Topics

This tutorial covers the following topics:

 Overview
 Prerequisites
 Configure a Simulator
 Monitor the Event Data
 Summary
 Related Information

Viewing Screenshots

 Place the cursor over this icon to load and view all the screenshots for this tutorial. (Caution: This action loads all screenshots simultaneously, so response time may be slow, depending on your Internet connection.)

Note: Alternatively, you can place the cursor over each individual icon in the following steps to load and view only the screenshot associated with that step.

Overview

Oracle Sensor Edge Server provides companies that want to adopt Radio Frequency Identification (RFID) technology with a comprehensive set of capabilities to capture, manage, analyze, access, and respond to data from different sensors such as RFID, location, and temperature. On the basis of Oracle's mature, proven technology (including Oracle Database 10g, Oracle Application Server 10g, Oracle Enterprise Manager 10g, and Oracle E-Business Suite 11 i), Oracle sensor-based services enable companies to quickly and easily integrate sensor-based information into their enterprise systems to gain near real-time supply chain visibility and leverage this insight to optimize business process.

The primary goal of the Sensor Edge Server is to transform raw data from the physical world into meaningful business events in your Enterprise Information System. This can be achieved in a closed loop, directly on the Sensor Edge Server, or by sending events to an Enterprise Information System. Access to the raw data and additional contextual and system information is always available through the data repository.

In this tutorial, you plug in a simulator driver in the driver framework to simulate the RFID reader. As a result of this integration, you see the events generated by the Sensor Edge Server and the simulation driver.

Back to Topic List

 

Prerequisites

Before starting this tutorial, you should:

1.

Have access to or have installed Oracle Application Server 10g Release 3 (10.1.3). You can download Oracle Application Server 10g 10.1.3 software from here.

2. Have access to or have installed Oracle Sensor Edge Server 10.1.3. You can download Oracle Sensor Edge Server software from here.

Back to Topic List

 

Configure a Simulator

Oracle Sensor Edge Server collects sensor information, filters it, and performs local sensor event processing. Oracle Sensor Edge Server then securely and reliably dispatches event data back to the central applications or databases. You perform Oracle Sensor Edge Server administration, configuration, and monitoring using the SES console.

The Edge Simulator Driver generates events to simulate a real device. You use the Edge Simulator Driver to test configurations and deployment designs. You can also use the simulator for internal functional testing to see how events are processed throughout the system. The Edge Simulator Driver emulates a regular driver. Except that instead of connecting to a physical device to read events, it takes parameters from an input file as instructions on when to generate false events. This simulator driver is very useful for testing and to see how events are processed throughout the system.

1.

Open your Browser and enter the following URL:

http://<hostname>.<domain>:8888/edge

Log in as oc4jadmin/<oc4jadmin password you specified during installation>. Click Login.

 

2.

Creating a device group is the first step to connecting the Oracle Sensor Edge Server instance to devices and filters. Once you create a device group, you populate it with devices (the instances of the available drivers) and then attach filter instances to the individual devices (or to the entire device group).
To create a new device group:
Click Groups.


3.

In the Group Management page, enter Streams in the Group Name field. Click Create New Group.

 

4.

The Configure Group page appears for the new device group. Click Add new device to create a device for the device group.

 

5.

The Search and Select: Add new device page appears, listing the drivers in the repository. Select Edge Simulator Driver. Click Select.

 

6.

The Configure Group page reappears, listing the device in the Devices section. Click Edge Simulator Driver1.

 

7.

The Device Configuration page appears, displaying the parameters specific to the driver.

 

8.

The Edge Simulator Driver generates events to simulate a real device. The Edge Simulator Driver behaves the same way as any driver, except that instead of connecting to a physical device to read events, it takes parameters from an input file such as Simulation.xml. The input file provides instructions about when to generate events.
Scroll down to the Parameters section. The simulator has one parameter that you need to set, which is the file name of the input file. Enter the path for the Simulation.xml file in the Value field of Filename parameter. Click Save Changes.

 

9.

A sample Simulation.xml file looks like this:

<EdgeEventSimulation>

<EventList repeat=’1’>

<Event>

<type>100</type>
<subtype>1</subtype>
<id>03ffff045679</id>
<data>No Data</data>
<deviceName>My Device</deviceName>

</Event>

.........

..........

...........

</EventList>

</EdgeEventSimulation>

The <EventList> element defines a loop. This element is also the main block that groups all the other instructions together. The <EventList> element has one attribute, repeat, which must be present to control looping. The value for repeat must be a decimal number from 0 to LONG_MAX.

The <EventInterval> element instructs the simulator to pause for a certain period of time before proceeding.

The <type> element represents the number value that corresponds to the type of event.

The <subtype> element represents the number value for the subtype. For example, the subtype value corresponds with a General Instruction Event, which is an event sent by the application or device to instruct a specific device to perform an operation. The value 1 turns on the device.

The <id> element represents a text value that identifies a tag (that is, a read or target) to an event instruction. One of the <id> values for a tag is 03ffff045679.

The <data> element is optional.

The <deviceName> element represents the name of the device or application that generates the event. The <deviceName> enables the simulator to appear as if it is another device when generating events.

 

10.

When you make any change in an Oracle Sensor Edge Server instance, the SES Console displays a message notifying you to restart the Oracle Sensor Edge Server instance using OracleAS Enterprise Manager. Click Enterprise Manager link in the message.

 

11.

The login page for OracleAS Enterprise Manager appears. Enter the OC4J user name and password. Click Login.

 

12.

Click the home link in the Cluster Topology page.

 

13.

Click Applications.

 

14.

Select edge and click Restart.

 

15.

Click Yes in the Confirmation page.

 

16.

Oracle Sensor Edge Server instance has been restarted successfully.

Click Logout to exit from Oracle Enterprise Manager.

 

Back to Topic List

Monitor the Event Data
1.

Verify that your OC4J server is running. If OC4J Server is not running, start the OC4J Server using the following command. Switch to the command prompt, change directory to <edgeserver_home>ORACLE_HOME\opmn\bin and issue the command:

opmnctl stopall

opmnctl startall

Open your browser, and enter the following URL:

http://< host name>.< domain>:< port>/edge

For example, http://localhost:8888/edge.

Log in as oc4jadmin with the OC4J administrator password that you specified during installation. Click Login.

 

2.

The SES console enables you to know the condition of Oracle Sensor Edge Server from the event data that is displayed on the Monitor Events and Event Reports tabbed pages. Click the Monitor Events tab to view the data currently in the queue. The inbound and outbound event data includes:
Type: Text representation of the event type
Description: A text representation of the event subtype
Device Name: The name of the device that generated the event
Data: The payload of the event
Time: The time that the event was generated

If no event has been generated, you will not view any event data under Inbound Queue and Outbound Queue.

 

Back to Topic List

Summary

 

In this lesson, you learned how to:

 Plug in a simulator to simulate an RFID device

Back to Topic List

Related Information

To learn more about Oracle Sensor Edge Server on Windows, you can refer to:

 Additional OBEs on the OTN Web site.

Back to Topic List

 Place the cursor over this icon to hide all screenshots.

 

 

 

Left Curve
Popular Downloads
Right Curve
Untitled Document