Installation Document

SensorWeb 2.0

Thee NOSA Project

Compiled by:
Ronald Siswara Wong
Jehanzeb Khan

Supervisor: Tom Kobialka

Contact Person email id: tkob@[Link]

Contents
1. Introduction______________________________________________________4
1.1. Purpose ___________________________________________________________ 4
1.2. How to Use This Document___________________________________________ 4
1.3. References_________________________________________________________ 4
1.4. Document Overview ________________________________________________ 4
2. Software Installation_______________________________________________5
2.1. TinyOS Installation on Windows XP ____________ Error! Bookmark not defined.
2.2. Install JNI Library for getenv _______________________________________ 22
2.3. Building TinyViz __________________________________________________ 22
2.4. Running TinyDB in the TOSSIM Simulator____________________________ 23
2.5. Installing Ant _____________________________________________________ 24
2.6. Installing Tomcat __________________________________________________ 24
2.7. Running the TOSSIM Simulation ____________________________________ 25
2.8. Running with the MOTES connected _________________________________ 26
2.9. Java Build Errors _________________________________________________ 26
2.10. JAR files ________________________________________________________ 27
2.11. Globus __________________________________________________________ 27
2.12. TcpTunnelGui ___________________________________________________ 27
2.13. SVN ____________________________________________________________ 27
2.14. Tomcat with eclipse edit ___________________________________________ 28
2.15. Logging _________________________________________________________ 28
2.16. Documentation ___________________________________________________ 28
3. Common Installation Problems _____________________________________29
3.1. Errors when compiling TinyOS ______________________________________ 29
3.2. Erros when executing TinyViz over the PC simulation ___________________ 29
3.3. TinyViz flash and dissapear _________________________________________ 32
3.4. Connection refused while running TinyDBMain java class _______________ 33
3.5. Exception when trying to start up Tomcat _____________________________ 34
3.6. Failed to Initialize SensorCollectionService ____________________________ 35
3.7. Axis Jar Problem __________________________________________________ 37
4. Postgres Installation ______________________________________________38
4.1. Set up ___________________________________________________________ 38
4.1.1. Step 0 - Setting Up Cygserver _____________________________________________ 38
4.1.2. Step 1. Start Cygserver for Shared Memory Support ___________________________ 38
4.1.3. Step 2. Create a New Database Cluster ______________________________________ 38
4.1.4. Step 3. Start up the postmaster ____________________________________________ 38
4.2. Command Notes___________________________________________________ 41
 4.3. Installing JDBC Driver _____________________________________________ 41
4.4. Running Postgres __________________________________________________ 41
4.5. Shutting Down Postgres ____________________________________________ 41
5. Getting the Services Running _______________________________________49
5.1. Before we start ____________________________________________________ 49
5.2. Configuring Eclipse ________________________________________________ 49
5.3. Machine Specific Configuration ______________________________________ 50
5.4. Building the NOSA Project__________________________________________ 51
5.5. Error Encountered When Building the NOSA Project ___________________ 52
5.6. Building the NOSA Project - 2 _______________________________________ 53
1. Introduction

1.1. Purpose
This document describes all the installation process for the SensorWeb 2.0 Software
starting from scratch. This document covers all aspect of its installation including all
various softwares needed, and how to deploy the web services in your machine.

1.2. How to Use This Document

When installing the SensorWeb 2.0 Software from scratch, readers are encouraged to
follow the order specified below:

• Section 2 (Not all software are compulsory and readers are encouraged to
check Section 3 when encounter some problems to see if they have already
been documented).

• Section 4 (This section could be skipped but most service and routine in
NOSA will not work without this).

• Section 5 (Compulsory)

1.3. References
• Various NOSA installation notes written by Tom Kobialka
• [Link]
• [Link]
• [Link]
• [Link]
• [Link]

1.4. Document Overview

The remainder of this document consists of the following sections:

• Section 2: Software Installation - All the various software that needs to be

installed before the NOSA service can be installed and deployed.

• Section 3: Common Installation Problems - Describe some of the common

problems encountered while following section 2 of this document.

• Section 4: Postgres Installation - Setting up the Postgres database to ensure it

is ready to be used by the service.

• Section 5: Getting the Services Running - All the configuration needed to

install and deploy the service in your machine.
2. Software Installation
2.1. Installing Intel Mote 2 Development Environment for
TinyOS 1.1 (Rev 5.0)
The Intel Mote 2 development environment requires Cygwin, Wasabi tool suite,
xflash programming tool and TinyOS/Nesc. The Intel Mote 2 platform code is
available
on sourceforge and can be downloaded from there. Please follow the detailed
instructions below to install and configure the development environment.
Step 1 – Installing Cygwin
1. Obtain the latest cygwin version from [Link]

2. Install cygwin at C:\tinyos\cygwin

3. Select options for “install for all users” and “use unix file types”.
4. By default, the Devel option doesn’t include the CVS options. Make sure you
go to the Devel list, and change the cvs, cvsps and cvsutil sublists from skip to
install. Also, select make sublist because it will be needed in step 6, Test the
Setup.

5. You need to install an editor for editing files. I chose three different editors to
try out.

6. You will need to install an utility for executing rpm command that is used for
installing NesC program in step 4 below.

7. Cygwin will point your home directory to “C:\Documents and

Settings\your_loginname”. This is liable to create problems with other apps,
 so change it to something like “/home/your_loginname”. This can be done by
editing the /etc/passwd file, scrolling down to the line that starts with
“your_loginname” and replacing the string “/cygdrive/c/Documents and
Settings/your_loginname” by “/home/your_loginname”. Restart cygwin and
check your home directory.

Here are the commands for editing passwd file with vi editor.

Note the directory below is already correct. I believe the above step for changing
passwd file is no longer necessary. Somebody must have installed a patch to
automatically perform this home directory correction. To exit vi editor without
saving changes, type “:q!” and depress enter key. To save changes and exit vi editor,
type “:wq” and depress enter key.

Step 2 – Downloading the TinyOS1.1 tree

1. If you already have an installation of the TinyOS1.1 tree from sourceforge,
just update the tree and proceed to step 3. Note: The next screen shot shows
directory of tinyos-1.x previously installed. I updated by running same code
in next step.
2. To install the TinyOS1.1 tree from scratch, go to c:/ and type the following:
cvs –z3 –d:pserver:anonymous@[Link]:/cvsroot/tinyos co –P
tinyos-1.x
 If you have an account on sourceforge, replace anonymous with your login
name and “pserver” with “ext”. When prompted for password enter your
password (or no password for the anonymous account, just press Enter key)

Note this will take a few minutes to download.

Step 3 – Configure TinyOS1.1 tree

1. The Intel Mote 2 platform files are split into a pxa27x and imote2
subdirectories and can be found in tinyos1.x/beta/platform/. Create a link to
each of these directories under tinyos1.x/tos/platform
a) Go to tinyos-1.x/tos/platform
b) Note space between “s ..”. Type: ln –s ../../beta/platform/imote2
imote2
c) Type: ln –s ../../beta/platform/pxa27x pxa27x

Screen shot shows platform’s directories before and after linking.

2. Setup the TOSDIR and TOSROOT variables in your .profile.
a) If you installed the tinyos tree in /cygdrive/c/tinyos-1.x, add the
following lines to your .profile file:
export TOSROOT=/cygdrive/c/tinyos-1.x
export TOSDIR=$TOSROOT/tos

Note: If you have installed the tinyos tree in a different location,

replace /cygdrive/c/tinyos-1.x with the path of your installed tree.

b) Set the new make utility to be your makefile by adding the following
line to your .profile:
export MAKERULES=$TOSROOT/tools/make/Makerules
Screen shot of .bash_profile before editing.
To edit .bash_profile with vi editor, use the below code:

Screen shot showing vi editor with three added lines of code. Note: To exit and save
changes while using vi editor, type “:wq” and depress enter key. After exiting vi
editor, you must restart cygwin for changes in .bash_profile to take effect.
Step 4 – Install NesC
1. Download NesC from the TinyOS website:
[Link] . Get the latest version nesc-
[Link] and load to a directory of your choice.

2. Using cygwin, navigate to your chosen directory and install using “rpm --
ignoreos –ivh [Link]”.

Step 5 – Install the Wasabi tool suite

1. The Wasabi toolsuite can be downloaded from
[Link]
a) Accept the license terms
b) Choose the Wasabi Systems Gnu Tools for Windows Host –
Elf generated binaries

c) Install the Wasabi tools to c:/wasabi

d) Add /cygdrive/c/wasabi/usr/local/bin to the beginning of
your path by adding the following to your .profile file:

PATH=/cygdrive/c/wasabi/usr/local/bin:$PATH
 e) Don't set GCC_EXEC_PREFIX like the user guide says.
Restart cygwin to make sure the path change has taken
effect.

f) Make sure that you can execute xscale-elf-gcc. To do

this refer to Wasabi_Xscale_Users_Guide1.pdf file and
follow step 3 of XP Installation section. Step shown
below. You can use a C-editor or text editor like
notepad. Save your file to the C drive. Note: Insert a
CD into CD drive or you will get an error about not being
able to read your CD drive. This is a known bug.

Results shown below:

Step 6 – Test the setup
1. Go to $TOSROOT/apps/blink
2. Type : make imote2 debug. It should complete but complain about dwarf2bd.
If it doesn’t complete and gives you an error message about an e drive : “cc1:
/cygdrive/e/wasabi_drops/…../include: No medium found”, insert a CD in
your e drive and try again. This is a known issue that we are trying to debug
currently. If it doesn't complete but you don’t get the error about the e drive,
check your environment variables.

Text outputted to cygwin terminal while executing ‘make imote2 debug’:

mkdir -p build/imote2
xscale-elf-as -mcpu=iwmmxt -mfpu=softfpa -defsym BOOTLOADER=1
/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/../imote2/flash.s /cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/../imote2/binarymover.s /cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/barecrt.s /cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/mmu_table.s /cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/util.s -o build/imote2/asms.o
cd /cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib; make;
make[1]: Entering directory `/cygdrive/c/tinyos-1.x/beta/platform/pxa27x/lib'
xscale-elf-gcc -g -O2 -Wall -I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x -
I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/DSP -I/cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/lib/ -c -o bufferManagement.o bufferManagement.c
xscale-elf-gcc -g -O2 -Wall -I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x -
I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/DSP -I/cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/lib/ -c -o downsample.o downsample.c
xscale-elf-gcc -g -O2 -Wall -I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x -
I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/DSP -I/cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/lib/ -c -o frequency.o frequency.c
xscale-elf-gcc -g -O2 -Wall -I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x -
I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/DSP -I/cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/lib/ -c -o paramtask.o paramtask.c
xscale-elf-gcc -g -O2 -Wall -I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x -
I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/DSP -I/cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/lib/ -c -o profile.o profile.c
xscale-elf-gcc -g -O2 -Wall -I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x -
I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/DSP -I/cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/lib/ -c -o queue.o queue.c
xscale-elf-gcc -g -O2 -Wall -I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x -
I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/DSP -I/cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/lib/ -c -o systemUtil.o systemUtil.c
xscale-elf-gcc -g -O2 -Wall -I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x -
I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/DSP -I/cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/lib/ -c -o utils.o utils.c
xscale-elf-gcc -g -O2 -Wall -I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x -
I/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/DSP -I/cygdrive/c/tinyos-
1.x/tos/platform/pxa27x/lib/ -c -o wmmx.o wmmx.c
xscale-elf-ar -rvs libimote2.a bufferManagement.o downsample.o frequency.o
paramtask.o profile.o queue.o systemUtil.o utils.o wmmx.o
r - bufferManagement.o
r - downsample.o
 r - frequency.o
r - paramtask.o
r - profile.o
r - queue.o
r - systemUtil.o
r - utils.o
r - wmmx.o
make[1]: Leaving directory `/cygdrive/c/tinyos-1.x/beta/platform/pxa27x/lib'
compiling Blink to a imote2 binary
ncc -o build/imote2/[Link] -g -fnesc-no-inline -I/cygdrive/c/tinyos-
1.x/tos/lib/CC2420Radio -I/cygdrive/c/tinyos-1.x/tos/lib/Flash -
DAUTO_BATTERY_MONITORING=1 -Wall -Wshadow -
DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=imote2 -fnesc-
cfile=build/imote2/app.c -board= -DBOOTLOADER -
DIDENT_PROGRAM_NAME=\"Blink\" -
DIDENT_USER_ID=\"MichaelZaremba\" -
DIDENT_HOSTNAME=\"ISU_Robotics\" -
DIDENT_USER_HASH=0xe8f84054L -DIDENT_UNIX_TIME=0x46af6ce8L -
DIDENT_UID_HASH=0x5d90bbfdL [Link] -lm build/imote2/asms.o
/cygdrive/c/tinyos-1.x/tos/platform/pxa27x/lib/libimote2.a
compiled Blink to build/imote2/[Link]
0 bytes in ROM
0 bytes in RAM
0 bytes in STACK
262144 bytes available in HEAP
xscale-elf-objcopy --output-target=binary build/imote2/[Link]
build/imote2/[Link]
dwarf2bd -nc build/imote2/[Link]
make: dwarf2bd: Command not found
make: *** [bin] Error 127

Note: Skip step 7, 8, 9 and 10 if using USB for programming. These steps are for
xflash programming with JTAG cable.

Skip step 7.
Step 7 – Test the setup again
• Go to $TOSROOT/apps/blink
• Type : make imote2 debug
• It should complete.
o If you get a dwarf2bd error, you probably didn’t restart your machine after
installing the SDT tools. Try restarting your machine and repeat the step
above. Note: [Link] is installed in c:\nordheim\xdbbin
o You can check if the path is setup correctly by typing which dwarf2bd at
the cygwin prompt, you should get /cygdrive/c/nordheim/xdbbin/dwarf2bd

Step 8 – Setup Intel Mote 2 debug board drivers

• The Intel Mote 2 debug/programming board contains a dual port FTDI chip to
map two of the mote UART ports to USB on your pc.
• Before connecting Intel Mote 2 debug board to your pc, download the drivers
from [Link] (for Windows XP). Current version is 2.02.04.
• Unzip the file to a folder.
• Connect the debug board to your computer via a USB cable. When prompted for a
driver, follow the installation instructions, specify the folder that you just
unzipped to look for a driver.

Device Manager results of loading drivers:

Skip step 9
Step 9 – Copy required files and setup the environment
• Copy [Link] and [Link] from $TOSROOT/contrib/imote2/installation to
c:\imote2
• Copy [Link] from $TOSROOT/contrib/imote2/installation to
C:\nordheim\xflash\[Link] (replace c:\norheim with your toolsuite location
if different)
• Copy [Link] from $TOSROOT/contrib/imote2/installation to
c:\nordheim\xflash\[Link] (overwrite existing file).
• If you have the Intel JTAG dongle, add the following line to your .profile file :
o export PXA27X_JTAG_DEV="\"INTEL(R) JTAG CABLE\""
Note, the INTEL JTAG cable might complain unless your PC has been hard
power cycled with its parallel port in ECP mode at base 0x378
• if you have a Macraigor Raven JTAG dongle, you don’t need to do anything.
Step 10 – Test the setup
• Restart Cygwin
• Plug in an Intel Mote 2 into the advanced connector of the debug board (J1 & J3).
• Push the power button on Intel Mote 2 (little button above the processor that
should be on the top side of the board when the mote is attached to the advanced
connectors.
• Go to tinyos-1.x/apps/Blink and type: make install imote2 debug.
• This will build, link and download the blink application to the Intel Mote 2.
• After the download is done, the mote should be blinking red at 2Hz (50% duty
cycle).

Step 11 – Load file to Intel Mote 2 using USBLoaderHost

1. Connect USB cable to Intel Mote 2.
2. Go to $TOSROOT/contrib/imote2/tools/bin directory.
3. Type:
‘./[Link] –p $TOSROOT/apps/Blink/build/imote2/[Link]’.

After program loads the led should flash red color.

Step 12 – Test the Intel Mote 2 debug shell

The Intel Mote 2 has a command shell that gets linked in by default to all
applications. This enables sending debug messages to a console, or invoking
commands in the mote from the console. The debug shell can be connected to
either the USB port on the mote (directly connecting the Intel Mote 2 to USB not
to the debug board), or through the UART (connecting the mote to the PC through
the debug board, hence going through the USB->UART translation). The two
approaches are mentioned below:

1. Debug through USB:

a. Connect the USB cable to the Intel Mote 2 board directly (J2) on one
side and to the PC on the other side.

b. Push the power button of the Intel Mote 2. The mote will be
recognized as a USB human interface device.

c. Use the ImoteConsole program to communicate with the mote, this can
be found in $TOSROOT/contrib/imote2/tools/bin directory.
i. You may have to do this first:
chmod a+x $TOSROOT/contrib/imote2/tools/bin/
[Link]

d. Start iMoteConsole by entering ./[Link].

e. Select the Imote2 from the drop down menu, the name of the device
will be “USB ID”, where ID is the least significant 4 digits of the serial
number shown on the back of the Intel Mote 2 board.

f. Click on “View Buffer In Window” option. This will start a new

window, push the Connect button. Go to the large box (click
anywhere inside the box), and push the enter button, you will see a
“BluSH>” prompt.

g. Type “ls” to see available commands. Type NodeID, the mote will
print out the serial number of the mote.
2. Debug through UART:
a. Connect the Intel Mote 2 to the programming board. If you installed
the programming board successfully in step 9 above, it will create two
“USB serial port” instances, you can find which COM ports were
mapped by going to control panel, system, hardware, device manager.
The ports will be listed under “Ports (COM & LPT)”. If you don’t see
these listed, please go back and check Step 9 above.

b. The second USB serial port listed is the one dedicated to the console.

c. Start hyperterm, choose the second com port listed and configure it to
115200, 8, none, 1, none.

d. Push the connect button. Push the enter button, you will see a
“BluSH>” prompt. Type NodeID, the mote will print out the serial
number of the mote.
2.2. Install JNI Library for getenv
To install JNI Library, execute:

> cd $TOSROOT/tools/java/jni
> make install

2.3. Building TinyViz

NOTE: For the rest of this document, all the commands are to be entered into the
Cygwin provided in the TinyOS installation setup

* We are going to create a PC simulation of TinyOS applications in TOSSIM.

(The next few steps are the shortlist of all the command line needs to be entered to
simulate it. Some explanations will be given but for more complete detailed
explanations, please refer to the document provided from TinyOS installation in:
$TOSROOT/doc/tutorial/[Link]).

> cd $TOSROOT/apps/TinyDBApp
> make pc

* Make TinyViz
> cd $TOSROOT/tools/java/net/tinyos/sim
> make

* Add TinyViz to your PATH

> export PATH=/opt/tinyos-1.x/tools/java/net/tinyos/sim:$PATH

* To test TinyViz go to:

> cd $TOSROOT/apps/TestTinyViz
> make pc
> export DBG=usr1
> tinyviz -run build/pc/[Link] 5
 * Execute TinyViz over the PC simulation
> cd $TOSROOT/apps/TinyDBApp
> export DBG=usr1
> tinyviz -run build/pc/[Link] 5

2.4. Running TinyDB in the TOSSIM Simulator

Now, we are going to run TinyDB in the TOSSIM Simulator. This section of the
document follows closely section 9 of TinyDB documentation "Running TinyDB in
the TOSSIM Simulator". Readers are encouraged to check that document as that
document contains much more detailed explanation than the one offered here.
The documentation is available from $TOSROOT/doc/[Link].

Inorder to run the TinyDB in the TOSSIM Simulator, we have to include the
following files in our classpath
C:\tinyos-1.x\tools\java\;
C:\[Link]; (This file should be downloaded from the following link)
C:\tinyos-1.x\tools\java\jars\; (This must be done in order for java to compile)
C:\tinyos-1.x\tools\java\jars\[Link];
C:\tinyos-1.x\tools\java\jars\[Link];
C:\tinyos-1.x\tools\java\jars\[Link];
C:\tinyos-1.x\tools\java\jars\[Link];
C:\tinyos-1.x\tools\java\jars\[Link];

* Recompile the java code under TinyDB

> cd $TOSROOT/tools/java/net/tinyos/tinydb
> make clean
> make -f MakePC

* Compile the PC Binary from the TinyDBApp application

> cd $TOSROOT/apps/TinyDBApp
> make -f MakePC pc

> export DBG=usr1

* Start the PC binary with n simulation nodes by typing

> ./build/pc/[Link] n
in the $TOSROOT/apps/TinyDBApp directory

* In a different shell window, we need to start the Java GUI in simulator

mode.
* However, before we run it, it is important for us to compile the
TinyDBMain Java class beforehand.
> cd $TOSROOT/tools/java/net/tinyos/tinydb
> make
 * NOTE: The above steps is not included in the TinyDB documentation
but it needs to be done before starting the Java GUI simulator
* Then, to run the Java GUI simulator simply type in the command
provided below

> cd $TOSROOT/tools/java
> java [Link] -sim

Assuming you set the DBG string as above, you should be able to click the "Reset
Motes" button and see a message in the window where you started the pc binary (the
first shell window) stating that reset is not supported in the simulator.

2.5. Installing Ant

Download Ant from [Link]

To install Ant, simply follow the instructions provided at

[Link]

Make sure ANT_HOME is set prior to building and don't forget to add
$ANT_HOME/bin to your $PATH

2.6. Installing Tomcat

• Download and install Tomcat (Windows Executable version) from
[Link]
at the time of writing this document, the version of the Tomcat I'm using is 5.5.20
• Do not use Tomcat Version 6.0 as it is missing the values for ‘[Link]’ and
‘[Link]’ in [Link] file.

• Additional installation instructions are available at

[Link]

• Set JAVA_HOME environment variable to point to the pathname of the directory

where the JRE is located. In my machine, the JAVA_HOME is set to C:\Program
Files\ Java\jdk1.5.0_02. Your JAVA_HOME may be different depending on
where you installed your JDK
Note that the installer will try to determine this package by default using the
registry but ensure manually that the location is correct for your machine

For the purposes of the remainder of this document, the symbolic name
"$CATALINA_HOME" is used to refer to the full pathname of the release
directory. As an example, in my computer, the symbol $CATALINA_HOME in
my computer represents C:\Program Files\Apache Software Foundation\apache-
tomcat-5.5.20
 NOTE: CATALINA_HOME represents the root of your tomcat installation.

• Add to /etc/[Link]:

> export CATALINA_HOME="/cygdrive/c/Program\ Files/Apache\

Software\ Foundation/Tomcat\ 5.5/

• To start up Tomcat in Windows simply execute the file

$CATALINA_HOME/bin/[Link]

• To shut it down, simply execute the file

$CATALINA_HOME/bin/[Link]

• Visit [Link] in you web browser to ensure tomcat is working

2.7. Running the TOSSIM Simulation

• Before running make sure that all the REAL sensor proxy references in;
/cygdrive/c/Program Files/Apache Software Foundation/Tomcat
5.5/webapps/SensorWeb/WEB-INF/classes/[Link] are
commented out and all references to db connector are uncommented.

This [Link] file will determine the execution path of the sensor
web services.

• Start tomcat:
/cygdrive/c/Program Files/Apache Software Foundation/Tomcat
5.5/bin/[Link]

should be able to see something [Link]

• Start TinyViz

> cd $TOSROOT/apps/TinyDBApp
> export DBG=usr1
> tinyviz -run build/pc/[Link] 5

• >> On First Execution run..

Edit Sensor-Source/[Link]
change classname to be:

classname=[Link]

• Now, to run DemoFrame execute, in Sensor-Source

(/cygdrive/c/workspace/Sensor-Source ) directory:
 > ant run

2.8. Running with the MOTES connected

• Edit [Link] under tomcat/webapps/SensorWeb/classes/WEB-
INF
uncomment all the lines that start with "REAL"

• Go to c:/Surge-View/

execute [Link]

set: serail@COM1:57600

• Ensure the motes and bass station are connected to the serial port

• Restart the server

• Open [Link] and go to Surge-View directory

• Execute:

> Surge 125 > [Link]

• Go to Sensor-Source directory and Execute

> ant run

• Select the second tab and press "Get Observation"

2.8.1. “Write Failed” Error while running Application with

SerialForwarder:
• Incase of “write failed” error, you will see a constant red light on your board
as well as motes. First make sure that the error is not in your code by going
through the tomcat trace logs. If the error is not in the code then you either
have to reset your board.

2.9. Java Build Errors

BUILD FAILED
[Link]: Unable to find a javac compiler;
[Link] is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK

Eclipse -> preferences ->Ant-> classpath

ensure that [Link] from the JDK you are using is located
in the classpath. If not go to "Add External Classpath"
and add it from c:/program files/java/jdk_1.5.0_2

2.10. JAR files

To extract files, including manifst file from jar archive, execute:

> jar xfv [Link]

To view contents of jar file, execute:

> jar tf [Link]

2.11. Globus
To setup Eclipse environment follow the guide “Using Eclipse to Develop Grid
Services” available at:
[Link]

To learn about grid services check out the “Borja’s Grid Services Tutorial” available
at:
[Link]

2.12. TcpTunnelGui
Follow these steps to use TcpTunnel for monitoring purpose:
1. Download [Link] from [Link]
2. Extract the file into directory of your choice (for me, it was C:\workspace\)
3. Run it

> cd /cygdrive/c/workspace/soap-2_3_1/lib
> java -cp [Link] [Link] 8081 localhost
8080

2.13. SVN
Start a new repository:
cd /home/projects/nosa/ (create this directory first!)
svnadmin create --fs-type fsfs svnrepository_1.0

svn import -m "Post- Techfest, with reworked SensorML repository code"

/home/staff/tkob/workspace_baseline_3_July_06/
[Link]
svnlook svn+ssh://[Link]/home/project
s/nosa/svnrepository_1.0

2.14. Tomcat with eclipse edit

To ensure tinyOS jars are copied into the wsrf/WEB-INF/lib
directory

add:
<copy toDir="${[Link]}">
<fileset dir="${[Link]}">
<include name="*.jar"/>
</fileset>
</copy>
under <target name="_baseTomcatDeploy"> (approx line 116)

under $GLOBUS_LOCATION/share/globus_wsrf_common/tomcat/[Link]

2.15. Logging
Change in /cygdrive/c/Program Files/Java/jdk1.5.0_02/jre/lib/[Link]
[Link] from FINE to Finest

2.16. Documentation
Documentation on Web Services
[Link]

When adding new webservices add to:

C:\Program Files\Apache Software Foundation\Tomcat
5.5\webapps\SensorWeb\WEB-INF\[Link]
3. Common Installation Problems
This section contains the common problem encountered while trying to install and
compile various software specified in Section 2.

3.1. Errors when compiling TinyOS

Problem:
When I tried to compile TinyOS, I get an error and the following scree of output is
displayed:

Global.h: In member function â~@~Xvoid TPt<TRec>::MkRef()â~@~Y:

Global.h:45: error: â~@~XNULLâ~@~Y was not declared in this scope
Global.h: In member function â~@~Xvoid TPt<TRec>::UnRef()â~@~Y:
Global.h:46: error: â~@~XNULLâ~@~Y was not declared in this scope
Global.h: In constructor â~@~XTPt<TRec>::TPt()â~@~Y:
Global.h:48: error: â~@~XNULLâ~@~Y was not declared in this scope
Global.h: In member function â~@~XTRec* TPt<TRec>::operator->()
constâ~@~Y: Global.h:59: error: â~@~XNULLâ~@~Y was not declared
in this scope
Global.h: In member function â~@~XTRec& TPt<TRec>::operator*()
constâ~@~Y: Global.h:60: error: â~@~XNULLâ~@~Y was not declared
in this scope
Global.h: In member function â~@~XTRec& TPt<TRec>::operator[](int)
constâ~@~Y: Global.h:61: error: â~@~XNULLâ~@~Y was not declared
in this scope

make[4]: *** [AvrDummy.o] Error 1

make[4]: Leaving directory `/home/tkob/tinyos-1.1.0/tools/src/uisp/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/tkob/tinyos-1.1.0/tools/src/uisp'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/tkob/tinyos-1.1.0/tools/src'
make[1]: *** [all-recursive] Error 2
make[1]: Leaving directory `/home/tkob/tinyos-1.1.0/tools'
make: *** [all] Error 2

Solution:
find the Globals.h file and edit it, replacing all instances of NULL with 0.

3.2. Erros when executing TinyViz over the PC simulation

Problem:
When i tried to execute TinyViz over the PC simulation I get an error and the
following screen of output is displayed

[root@rubyoureyes TestTinyViz]# tinyviz -run build/pc/[Link] 5

java -[Link]=/tmp/[Link] -DDBG=usr1 -DSIMDBG= -
jar
/usr/local/share/tinyos-1.x/tools/java/net/tinyos/sim/[Link] -gui -run
build/pc/[Link] 5
Starting SimDriver...
Simulation random seed 449570990
Initializing simulator objects...
Could not find a platform specific version of TOSMsg
[Link]: [Link]
[Link]: [Link]
at [Link]([Link])
at [Link]([Link])
at [Link]$[Link]([Link])
at [Link]([Link])
at [Link].forName1(Native Method)
at [Link]([Link])
at
[Link](MessageFactory.j
ava:122)
at
[Link]([Link]:
44)
at [Link].<init>([Link])
at [Link].<init>([Link])
at [Link]([Link])
Loading simulator plugins...
Creating TinyViz GUI...

Welcome to Tython. Type 'quit' to exit.

ESC on a line by itself will pause/resume the simulator.

>>> AUTORUN: Initializing simulation.

AUTORUN: Running simulation: build/pc/[Link] -gui -r=lossy -
seed=449570990
-nodbgout 5
AUTORUN: Connecting...
SimComm: TossimInitEvent received (5 motes)... initializing system.
SimComm: Pausing system for TossimInitEvent
AUTORUN: Simulation running.
Could not find a platform specific version of TOSMsg
[Link]: [Link]
[Link]: [Link]
at [Link]([Link])
at [Link]([Link])
at [Link]$[Link]([Link])
at [Link]([Link])
at [Link].forName1(Native Method)
at [Link]([Link])
 at
[Link](MessageFactory.j
ava:122)
at
[Link]([Link]:
36)
at
[Link].<init>([Link])
at [Link].<init>([Link])
at
[Link].<init>([Link]
:32)
at [Link].newInstance0(Native
Method)
at
[Link](NativeConstruct
[Link])
at
[Link](DelegatingC
[Link])
at [Link]([Link])
at
[Link]([Link])
at
[Link]([Link])
at
[Link]([Link]
77)
at
[Link]([Link])
at [Link]([Link])
at [Link]([Link])
Built a Packet source for avrmote
Could not find a platform specific version of TOSMsg
[Link]: [Link]
[Link]: [Link]
at [Link]([Link])
at [Link]([Link])
at [Link]$[Link]([Link])
at [Link]([Link])
at [Link].forName1(Native Method)
at [Link]([Link])
at
[Link](MessageFactory.j
ava:118)
at
[Link]([Link]:
44)
at [Link]([Link])
at [Link]([Link])
 [Link]
&nbsp; at
[Link]([Link])
at [Link]([Link])
AUTORUN: Process exited.
AUTORUN: Done with run.

Solution:

Edit the file: $TOSROOT/tools/java/net/tinyos/sim/Makefile

Add:
$ diff -u [Link] Makefile
--- [Link] 2004-03-02 [Link].000000000 -0500
+++ Makefile 2004-10-18 [Link].000000000 -0400
@@ -53,6 +53,7 @@
net/tinyos/util/*.class \
net/tinyos/packet/*.class \
net/tinyos/message/*.class \
+ net/tinyos/message/avrmote/*.class \
org/apache/oro/text/regex/*.class \
org/python/compiler/*.class \
org/python/core/*.class \

Note: If you don't understand what the above means, simply add the following line to
your makefile in the place shown above
net/tinyos/message/avrmote/*.class
Then, In the same directory execute:

> make

3.3. TinyViz flash and dissapear

Problem:
When executing TinyViz, it flash and disappears with the following screen output.

Starting SimDriver...
SimComm: TossimInitEvent received (5 motes)... initializing system.
SimComm: Pausing system for TossimInitEvent
DRIVER: Can't use AutoRun when SimComm already connected
(check for stale [Link] processes)

Solution:
Simply open task manager and end [Link] task. Then just try it again. This is most
likely happen because you end the previous TinyViz application prematurely.
3.4.
Connection refused while running TinyDBMain java class
Problem:
I have followed the TinyDB documentation provided in $TOSROOT/doc/[Link]
and when I execute the command below, it gives me a weird error telling me that
connection is refused. Whats wrong with it ? I have read every single documentation
available but there is nothing that mention this kind of problem.

> java [Link]

The output is displayed below:

Opening tossim-serial source

Connecting to Tossim event port at localhost:10585
[Link]: Connection refused: connect
at [Link](Native Method)
at [Link]([Link])
at
[Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link].<init>([Link])
at [Link].<init>([Link])
at
[Link]([Link])
at [Link]([Link])
at [Link]([Link])
tossim-serial@localhost died - restarting
[Link]: Connection refused: connect
at [Link](Native Method)
at [Link]([Link])
at
[Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link].<init>([Link])
at [Link].<init>([Link])
at
[Link]([Link])
at [Link]([Link])
at [Link]([Link])

Solution:
If you read the TinyDB documentation carefully, you may notice that when they run
the TinyDBMain class, they had already install TinyDB on a mote. That mote is the
one that we are trying to connect. Obviously now you may realize that we get this
problem simply because we have nothing that we try to connect to. So how do we go
around this? What we need to do is to simulate the mote. Please ensure that you have
run the PC binary simulation before you run the TinyDBMain class. That PC binary
will simulate the motes that we need.

3.5. Exception when trying to start up Tomcat

Problem:
When I tried to start up Tomcat using the [Link] in the $CATALINA_HOME
folder, it gives me the following error

SEVERE: Error initializing endpoint

[Link]: Address already in use: JVM_Bind:8080
at
[Link](PoolTcpEndpoi
[Link])
at
[Link]([Link]
va:138)
at
[Link]([Link])
at
[Link]([Link]
80)
at
[Link]([Link]
1)
at [Link]([Link])
at [Link]([Link])
at [Link].invoke0(Native Method)
at
[Link](NativeMethodAccessorIm
[Link])
at
[Link](DelegatingMethodAc
[Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
Dec 19, 2006 [Link] PM [Link] load
SEVERE: [Link]
LifecycleException: Protocol handler initialization failed:
[Link]: Address already in use: JVM_Bind:8080
at
[Link]([Link])
at
[Link]([Link]
80)
at
[Link]([Link]
 1)
at [Link]([Link])
at [Link]([Link])
at [Link].invoke0(Native Method)
at
[Link](NativeMethodAccessorIm
[Link])
at
[Link](DelegatingMethodAc
[Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])

Solution:
This is one of the most common problems found in using Tomcat. This happens
simply because there is another web server (or any other process) that has already
claimed port 8080. This can also occur when you have already started a Tomcat
previously and didn't shut it down properly. To shut it down properly, use the script
[Link] available at $CATALINA_HOME/bin

To find out more solution for this issue, please refer to

$CATALINA_HOME/[Link]

3.6. Failed to Initialize SensorCollectionService

Problem:

Failed to initialize 'globus/SensorCollectionService' service. Caused by

[Link]:
[Link]
sorCollectionService
at [Link].newInstance0([Link])
at [Link]([Link])
at
[Link](RPCProvi
[Link])
at
[Link](ServiceDe
[Link])
at
[Link](ServiceDesc
[Link])
at
[Link]$[Link](
[Link])
at
[Link](ServiceMana
 [Link])
at
[Link]([Link]
)
at
[Link]([Link]
31)
at
[Link]([Link]
37)
at
[Link].<init>([Link]:
195)
at
[Link].<init>(GSIServiceContai
[Link])
at [Link].newInstance0(Native
Method)
at
[Link](NativeConstruct
[Link])
at
[Link](DelegatingC
[Link])
at [Link]([Link])
at
[Link](ServiceConta
[Link])
at
[Link](Servic
[Link])
at
[Link]([Link]
03)
at [Link].invoke0(Native Method)
at
[Link](NativeMethodAccessorIm
[Link])
at
[Link](DelegatingMethodAc
[Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])

Solution:
All my classes weere mixed up. My org_sensorweb_sensor_collectionsevice.jar
file had no content! I fixed this by following Borja's tutorial more closely and
modifying my class paths in my wsdl file to more closely align with his. Special care
was taken to separate my actual implementation (.impl) from the generated stubs.
Which is what I got mixed up.

3.7. Axis Jar Problem

Problem:

Exception in thread "main" [Link]:

[Link].<init>(Ljava/lang/Class;Z)V
at
[Link].<clinit>(End
[Link])
at
[Link](SensorWebCl
[Link])

Solution:
Different [Link] files where being used to compile my code, compared to those used
to execute my code. I followed the Eclipse grid services document to create a new
project where I had complete control over my jar files.
4. Postgres Installation
This section contains guide on set up and initialisation of PostgreSQL 7.4.5 under
Cygwin / Windows XP

Note that the postgres package that we need to use is PostgreSQL is the version 7.4.5
and it is already included in the TinyOS default install.

4.1. Set up
4.1.1. Step 0 - Setting Up Cygserver
Type in the following command in your Cygwin

> export CYGWIN=server

> cygserver-config

Note that a client application which wants to use the services provided by cygserver
*must* have the environment variable CYGWIN set so that it contains the word
"server". So if you don't need any other special CYGWIN setting, just set it to
"server".

It is advisable to add this setting to the Windows system environment.

4.1.2. Step 1. Start Cygserver for Shared Memory Support

To do this, enter the command:

> /usr/sbin/[Link] &

This program needs to be running anytime you start the PostgreSQL server
(postmaster) or initialize a database (initdb).

4.1.3. Step 2. Create a New Database Cluster

Use the initdb command to create a new database cluster.
Enter the following command in your cygwin which will create a new database
cluster in the /var/postgresql/data directory

> /usr/sbin/initdb -D /var/postgresql/data -W

NOTE: As a reference, a database cluster is a database storage area on disk. This is a

collection of databases accessible by a single instance of a running database server

4.1.4. Step 3. Start up the postmaster

We can now start the database server using one of the following command
 > /usr/sbin/postmaster -D /var/postgresql/data

or

> /usr/sbin/postmaster -D /var/postgresql/data >logfile 2>&1 &

The first command will leave the server running into the foreground while the second
command will start the postmaster in the background. Note also that the second
command will redirect the entire log message to the file called logfile.

This will start the postmaster, and if successful you will see some initial log entries,
and an entry "LOG: database system is ready".
Before anyone can access the database, you must start the database server (i.e.
postmaster).

NOTE: For some of the common problems associated with postmaster start up failure,
please refer to [Link]

* Create Users:
Note: This is not totally necessary, by default the user that
executed createdb will already be in the database, however you
may want to set a password (see below).

> CREATE USER tkob;

Use:
> DROP USER name;
to remove a user.

Command line equivalents also exist:

createuser name
dropuser name

To list users in database:

"select * from pg_user;" OR \du

* Set password:
ALTER USER tkob PASSWORD '********';

Step 4. Create a Database

 > createdb sensorml_repository ----DONE

To remove a database:

dropdb sensorml_repository

Once you have created a database, you can access it by running the PostgreSQL
interactive terminal program, called psql, which allows you to interactively enter, edit,
and execute SQL commands

> psql sensorml_repository

NOTE: this is for terminal access only, for in-program access you will need to use the
java connector ([Link]

For help:

> mydb=> \h

To get out of psql, type

> mydb=> \q

To read in SQL commands from a specific file:

> mydb=> \i sensorml_db_populate.sql

Commands:

\l - list all databases on server

Use a Specific Database: \c databaseName;

List All Objects in the Database: \d

List Tables: \dt

(or \d[ivsS] to list indexes, views, sequences, Schema objects)

Count All Rows in a Table: select count(*) from tableName;

List All Rows in a Table: select * from tableName;

4.2. Command Notes
To remove a table:

> DROP TABLE tablename;

The INSERT statement is used to populate a table with rows

UP TO: [Link]

4.3. Installing JDBC Driver

This will allow your Java code to talk to Postgres:

> cd /cygdrive/c/workspace/Sensor -Source/lib

> cp /usr/share/postgresql/java/[Link] .

!!!IMPORTANT:!!!
Because Java only uses TCP/IP connections, the PostgreSQL server must be
configured to accept TCP/IP connections. This can be done by setting tcpip_socket =
true in the [Link] file or by supplying the -i option flag when starting
postmaster.

Also: uncomment Port 5432 in configuration file.

4.4. Running Postgres

> export CYGWIN=server
> /usr/sbin/cygserver &
> /usr/sbin/postmaster -i -D /var/postgresql/data &

-i allows clients to connect over TCP/IP as opposed to just those from the local
machine.

4.5.
Shutting Down Postgres
> pg_ctl stop -w -D /var/postgresql/data -s -m smart
> kill $(ps -f | grep cygserver | awk '{print $2}')

--Place the text below in sensorml_db_populate.sql under cygwin directory

-- Tom Kobialka tkob@[Link]

-- NICTA SensorWeb Project
-- 10th April 2006

-- Skeleton SQL TABLEs for SensorML Repository

-- Postgres Startup
-- ================
-- export CYGWIN=server
-- /usr/sbin/cygserver &
-- postmaster -i -D /var/postgresql/data &

-- Postgres Shutdown
-- =================
-- pg_ctl stop -w -D /var/postgresql/data -s -m smart
-- kill $(ps -f | grep cygserver | awk '{print $2}')

CREATE TABLE Sensor(

SensorId varchar(80) PRIMARY KEY -- Sensor ID
);

CREATE TABLE StationaryPlatform(

PlatformId varchar(80) PRIMARY KEY -- Platform ID
);

CREATE TABLE PlatformDescription(

PlatformId varchar(80) REFERENCES StationaryPlatform (PlatformId), --
Forigen Key
descriptionContent varchar(250)
);

CREATE TABLE namespace(

SensorId varchar(80) REFERENCES Sensor (SensorId),
nsPrefix varchar(80),
nsUri varchar(250)
);

CREATE TABLE SensorDescription(

SensorId varchar(80) REFERENCES Sensor (SensorId), -- Forgien Key
descriptionContent varchar(250)
);

CREATE TABLE identification(

SensorId varchar(80) REFERENCES Sensor (SensorId), -- Forgien Key
identifierName varchar(80),
idTermQualifier varchar(80),
idTermContent varchar(80)
);

CREATE TABLE classification(

SensorId varchar(80) REFERENCES Sensor (SensorId), -- Forgien Key
 classifierName varchar(80),
clTermQualifier varchar(80),
clTermContent varchar(80)
);

CREATE TABLE inputs(

SensorId varchar(80) REFERENCES Sensor (SensorId), -- Forigen Key
inputId varchar(80) PRIMARY KEY
);

CREATE TABLE inputList(

inputId varchar(80) REFERENCES inputs (inputId),
inputName varchar(80),
inputType varchar(80),
inputDefinition varchar(80),
inputUom varchar(80),
min int,
max int
);

CREATE TABLE outputs(

SensorId varchar(80) REFERENCES Sensor (SensorId), -- Forigen Key
outputId varchar(80) PRIMARY KEY
);

CREATE TABLE outputList(

outputId varchar(80) REFERENCES outputs (outputId),
outputName varchar(80),
outputType varchar(80),
outputDefinition varchar(80),
outputUom varchar(80),
min int,
max int
);

CREATE TABLE method(

methodId varchar(80) REFERENCES Sensor (SensorId), -- Forigen Key
methodName varchar(150)
);

-- Tom Kobialka tkob@[Link]

-- NICTA SensorWeb Project
-- 23 June 2006

-- Sample Data
-- Manual Insertion into Postgres database.. Should be done dynamically

-- Postgres Startup
-- ================
-- export CYGWIN=server
-- /usr/sbin/cygserver &
-- postmaster -i -D /var/postgresql/data &

-- Postgres Shutdown
-- =================
-- pg_ctl stop -w -D /var/postgresql/data -s -m smart
-- kill $(ps -f | grep cygserver | awk '{print $2}')

-- WorkStation
INSERT INTO Sensor VALUES('Sensor_126');
INSERT INTO namespace
VALUES('Sensor_126','sml','[Link]
INSERT INTO namespace
VALUES('Sensor_126','gml','[Link]
INSERT INTO namespace
VALUES('Sensor_126','swe','[Link]

INSERT INTO StationaryPlatform VALUES('Platform_126');

INSERT INTO PlatformDescription VALUES('Platform_126','Dell
Workstation, PC 686, Melbourne University 2006');

INSERT INTO SensorDescription VALUES('Sensor_126','No Sensors are

installed on the workstation');
INSERT INTO identification
VALUES('Sensor_126','longName','urn:og[Link]identifier:longName','Workstati
on');
INSERT INTO classification
VALUES('Sensor_126','longName','urn:og[Link]lassifier:observationClassifica
tion','in-situ');

INSERT INTO inputs VALUES('Sensor_126','Sensor_126');

INSERT INTO inputList
VALUES('Sensor_126',NULL,NULL,NULL,NULL,NULL,NULL);

INSERT INTO outputs VALUES('Sensor_126','Sensor_126');

INSERT INTO outputList
VALUES('Sensor_126',NULL,NULL,NULL,NULL,NULL,NULL);

INSERT INTO method

VALUES('Sensor_126','urn:og[Link]process:1.0:sensor');

-- Base Station
INSERT INTO Sensor VALUES('Sensor_0');
INSERT INTO namespace
VALUES('Sensor_0','sml','[Link]
INSERT INTO namespace
VALUES('Sensor_0','gml','[Link]
INSERT INTO namespace
VALUES('Sensor_0','swe','[Link]
INSERT INTO namespace
VALUES('Sensor_0','xLink','[Link]

-- Platform
INSERT INTO StationaryPlatform VALUES('Platform_0');
INSERT INTO PlatformDescription VALUES('Platform_0','Crossbow
MIB510CA Base Station for Mica2 Motes with MPR400CB receiver, copyright
2003');

-- Sensors
INSERT INTO SensorDescription VALUES('Sensor_0','Crossbow Sensor 0
node, Mica Sensor board MTS300CA');
INSERT INTO identification
VALUES('Sensor_0','longName','urn:og[Link]identifier:longName','Base
Station');
INSERT INTO classification
VALUES('Sensor_0','longName','urn:og[Link]lassifier:observationClassificatio
n','in-situ');

INSERT INTO inputs VALUES('Sensor_0','Sensor_0');

INSERT INTO inputList
VALUES('Sensor_0','nodeid','Count','urn:og[Link]ta:index',NULL,'0','1000');
INSERT INTO inputList
VALUES('Sensor_0','temperature','Quantity','urn:og[Link]phenomenon:temperat
ure','urn:og[Link]unit:celcius',NULL,NULL);
INSERT INTO inputList
VALUES('Sensor_0','light','Quantity','urn:og[Link]illumination','urn:og[Link]unit
:lux',NULL,NULL);

INSERT INTO outputs VALUES('Sensor_0','Sensor_0');

INSERT INTO outputList
VALUES('Sensor_0','measuredNodeid','Count','urn:og[Link]ta:index',NULL,'
0','1000');
INSERT INTO outputList
VALUES('Sensor_0','measuredTemperature','Quantity','urn:og[Link]phenomeno
n:temperature','urn:og[Link]unit:celcius',NULL,NULL);
INSERT INTO outputList
VALUES('Sensor_0','measuredLight','Quantity','urn:og[Link]illumination','urn:o
g[Link]unit:lux',NULL,NULL);

INSERT INTO method VALUES('Sensor_0','urn:og[Link]process:1.0:sensor');

-- Sensor 1
INSERT INTO Sensor VALUES('Sensor_1');
INSERT INTO namespace
VALUES('Sensor_1','sml','[Link]
INSERT INTO namespace
VALUES('Sensor_1','gml','[Link]
INSERT INTO namespace
VALUES('Sensor_1','swe','[Link]
INSERT INTO namespace
VALUES('Sensor_1','xLink','[Link]

-- platform
INSERT INTO StationaryPlatform VALUES('Platform_1');
INSERT INTO PlatformDescription VALUES('Platform_1','MPR400CB 2003
Crossbow receiver');

-- sensors
INSERT INTO SensorDescription VALUES('Sensor_1','Crossbow Sensor 1
node, Mica Sensor board MTS300CA');
INSERT INTO identification
VALUES('Sensor_1','longName','urn:og[Link]identifier:longName','Sensor 1');
INSERT INTO classification
VALUES('Sensor_1','longName','urn:og[Link]lassifier:observationClassificatio
n','in-situ');

INSERT INTO inputs VALUES('Sensor_1','Sensor_1');

-- INSERT INTO inputList
VALUES('Sensor_1','nodeid','Count','urn:og[Link]ta:index',NULL,'0','1000');
INSERT INTO inputList
VALUES('Sensor_1','sound','Quantity','urn:og[Link]sound','urn:og[Link]unit:dB',
NULL,NULL);
INSERT INTO inputList
VALUES('Sensor_1','light','Quantity','urn:og[Link]illumination','urn:og[Link]unit
:lux',NULL,NULL);

INSERT INTO outputs VALUES('Sensor_1','Sensor_1');

--INSERT INTO outputList
VALUES('Sensor_1','measuredNodeid','Count','urn:og[Link]ta:index',NULL,'
0','1000');
--INSERT INTO outputList
VALUES('Sensor_1','measuredTemperature','Quantity','urn:og[Link]phenomeno
n:temperature','urn:og[Link]unit:celcius',NULL,NULL);
INSERT INTO outputList
VALUES('Sensor_1','measuredLight','Quantity','urn:og[Link]illumination','urn:o
g[Link]unit:lux',NULL,NULL);
INSERT INTO outputList
VALUES('Sensor_1','measuredSound','Quantity','urn:og[Link]sound','urn:ogc:de
f:unit:dB',NULL,NULL);

INSERT INTO method VALUES('Sensor_1','urn:og[Link]process:1.0:sensor');

-- Sensor 2
INSERT INTO Sensor VALUES('Sensor_2');
INSERT INTO namespace
VALUES('Sensor_2','sml','[Link]
INSERT INTO namespace
VALUES('Sensor_2','gml','[Link]
INSERT INTO namespace
VALUES('Sensor_2','swe','[Link]
INSERT INTO namespace
VALUES('Sensor_2','xLink','[Link]
-- platform
INSERT INTO StationaryPlatform VALUES('Platform_2');
INSERT INTO PlatformDescription VALUES('Platform_2','MPR400CB 2003
Crossbow receiver');

-- sensors
INSERT INTO SensorDescription VALUES('Sensor_2','Crossbow Sensor 2
node, Mica Sensor board MTS300CA');
INSERT INTO identification
VALUES('Sensor_2','longName','urn:og[Link]identifier:longName','Sensor 2');
INSERT INTO classification
VALUES('Sensor_2','longName','urn:og[Link]lassifier:observationClassificatio
n','in-situ');

INSERT INTO inputs VALUES('Sensor_2','Sensor_2');

-- INSERT INTO inputList
VALUES('Sensor_2','nodeid','Count','urn:og[Link]ta:index',NULL,'0','1000');
INSERT INTO inputList
VALUES('Sensor_2','sound','Quantity','urn:og[Link]sound','urn:og[Link]unit:dB',
NULL,NULL);
INSERT INTO inputList
VALUES('Sensor_2','temperature','Quantity','urn:og[Link]phenomenon:temperat
ure','urn:og[Link]unit:celcius',NULL,NULL);

INSERT INTO outputs VALUES('Sensor_2','Sensor_2');

--INSERT INTO outputList
VALUES('Sensor_2','measuredNodeid','Count','urn:og[Link]ta:index',NULL,'
0','1000');
INSERT INTO outputList
VALUES('Sensor_2','measuredTemperature','Quantity','urn:og[Link]phenomeno
n:temperature','urn:og[Link]unit:celcius',NULL,NULL);
INSERT INTO outputList
VALUES('Sensor_2','measuredSound','Quantity','urn:og[Link]sound','urn:ogc:de
f:unit:dB',NULL,NULL);

INSERT INTO method VALUES('Sensor_1','urn:og[Link]process:1.0:sensor');

========================================================
Drop scripts should be placed in some other file.
========================================================

DROP TABLE method CASCADE;

DROP TABLE outputs CASCADE;
DROP TABLE outputList CASCADE;
DROP TABLE inputs CASCADE;
DROP TABLE inputList CASCADE;
DROP TABLE SensorDescription CASCADE;
DROP TABLE PlatformDescription CASCADE;
DROP TABLE namespace CASCADE;
DROP TABLE classification;
DROP TABLE identification;
DROP TABLE StationaryPlatform;
DROP TABLE sensor;
DROP TABLE historic_observation;
DROP TABLE user_table;
DROP TABLE id_table;
========================================================
Scripts should be placed in separate file.
========================================================
-- Tom Kobialka tkob@[Link]
-- NICTA SensorWeb Project
-- 12th December 2006

-- Skeleton SQL TABLEs for Sensor Repository Service user repository

CREATE TABLE historic_observation(

nodeid varchar(20),
light varchar(20),
temperature varchar(20)
);

-- Tom Kobialka tkob@[Link]

-- NICTA SensorWeb Project
-- 31st October 2006

-- Skeleton SQL TABLEs for Web Notification Service user repository

CREATE TABLE user_table(

id varchar(20),
name varchar(80),
contact varchar(80)
);

CREATE TABLE id_table(

id varchar(20)
);
5. Getting the Services Running
5.1. Before we start
The NOSA codes require JDK 1.5.0_02. They won’t work under JDK 1.4 You need
to make sure to set this as your default Java. To set it as your default JAVA, point the
environment variable JAVA_HOME and PATH appropriately. Make sure also that
Ant and Tomcat refers to JDK 1.5.0_02 in case you have more than one Java installed
on your machine.

5.2. Configuring Eclipse

Firstly, install Eclipse and Globus following documentation. It is also helpful to
configure Eclipse to be able to develop grid services. Follow the documentation
provided in [Link] for guide on how to configure
Eclipse to develop grid services.

Then you need to make sure also to get tomcat running with eclipse. The guide to do
that can be found in the same guide provided above.

Importing the NOSA codes

All the codes are located in NOSA directory.

To start with, you should have been given the NOSA directory containing all the
codes. If you are using Eclipse and you are just starting out, start by importing the
Project into your workspace. Choose File->Import. In the dialog, choose General-
>Existing Projects into Workspace. Follow the prompt as appropriately.

Rearrange the directory.

tinyos-lib contains the library file that you will need. Just place it into the same
directory as NOSA as depicted above

It should also be in the same directory as ws-core-4.0.2

This is the way I arrange my workspace:

Workspace
- ws-core-4.0.3
- NOSA
- tinyos-lib
- Surge-View

3 Errors encountered after importing SensorWeb 2.0 Software into my workspace

Severity and Path Resource / Location Creation Time Id

Description Folder
Name
The project NOSA Unknown 1167767733390 26
cannot be
built until
build path
errors are
resolved
Unbound NOSA Build path 1167767756859 77
classpath
container:
'GT4' in
project
NOSA
Unbound NOSA Build path 1167767756859 78
classpath
container:
'Tiny-OS' in
project
NOSA

The first error is caused by the next two errors so we will need to fix those errors.

Unbound classpath container is caused by the fact that Eclipse could not find these
libraries (this could be defined as user libraries previously).
To check this, [Link] file from NOSA directory and see if there are two user
libraries with the name of GT4 and Tiny-OS defined there.

What we need to do is to update the Java Build Path libraries to include those GT4
and Tiny-OS libraries. By doing so will enable the Eclipse editor to find those classes
that NOSA sources will import.

Go to Project->Properties page. Select the Java Build Path page and click the
Libraries tab. You would notice that all those libraries will be listed and there are two
unbound libraries which are GT4 and Tiny-OS itself.

Fix each one of them by clicking Edit. In the dialog that comes up, choose the user
library for each of them. If it is empty, you will need to create a new user library for
each of them. For the GT4 library, create a new user library with the name GT4
Library, then click the button Add JARs and select and add all of the JARs in
$GLOBUS_LOCATION\lib to the library. Selecting OK and Finish leaves us with
the properly configured Libraries tab. The GT4 library should not be unbounded
anymore. Note that $GLOBUS_LOCATION refer to the location where your GT4 is
installed.

Do the similar thing with Tiny-OS library. The only difference is that, add the JARs
from the tinyos-lib provided together with NOSA.

5.3. Machine Specific Configuration

Some machine specific configuration will needs to be done since some variable is
hardcoded and some folder location could be different in two different machine
First, open some of the files listed below and change some of the variable to suit your
machine. The comments in each file will help you determine which path to be
changed.

• [Link]:
o [Link]
o [Link]
o [Link]
• [Link]:
o [Link] (Note that there are more than 1 occurrences of this
variable to be changed. In fact, there are 4 occurrences of them)
• [Link]:
o [Link]

Note also that you might need to edit build_***.xml if hard coded path elements exist
(if we miss anything)

Note that [Link] uses [Link] for configuration. You will

need to set your paths in this file.

You also need to add [Link] to your Java build path in Eclipse. Go to
Window->Preferences then choose Java->Build Path->Classpath Variables. Add new
variable entries for GLOBUS_LOCATION and APPLICATION_PROPERTIES. For
GLOBUS_LOCATION, point it to the location of the GT4 folder (it is
C:/workspace/ws-core-4.0.3/ in my machine). For APPLICATION_PROPERTIES,
point it to the location of $NOSA/[Link] where NOSA represents the
location of NOSA source code. You may need to type the location directly instead of
using the file selector.

5.4. Building the SensorWeb 2.0 Software

Run Ant on [Link]. Start the building target starting from the bottom target.

In [Link], we have the following build targets:

<!--<target name="all" depends="SensorPlanningService" />-->

<!--<target name="all" depends="SensorCollectionService" />-->
<!--<target name="all" depends="SensorRepositoryService" />-->
<!--<target name="all" depends="WebNotificationService" /> -->

Initially, uncomment the bottom target (remove the <!-- and -->) and execute Ant
build on it.

After that is built, comment the bottom line and uncomment the next above that. Keep
on doing that until you reach the top.

In other words, this is the sequence order on which the build should be executed:
1. WebNotificationService
2. SensorRepositoryService
 3. SensorCollectionService
4. SensorPlanningService

To execute Ant build on the targets, follow the instructions given in the tutorial for
building grid services using Eclipse. (this is the link in case you forget it already
[Link]

5.5. Error Encountered When Building the SensorWeb 2.0

Software

Error:
The eclipse editor shows red compilation errors on the package [Link] and all the
other class that is imported from that package.

Solution:
The problem comes from the fact that Eclipse couldn’t see the package [Link].
When you install TinyOS, [Link] file is included in $TOSROOT/tools/java/jars.
Add this jar as a new user library to silence all those Editor View’s red compile
errors. Ensure that you use the [Link] provided by TinyOS

Error:
When I tried built the target, it gives me many compilation errors. From closer looks,
it seems that most of the problem is because Eclipse couldn’t find the package
[Link].

Solution:
This is because Eclipse could see the package but Ant could not see the package. One
solution to this would be to add all the jars to Ant CLASSPATH. One way of doing it
is to go to Window->Preferences. In the dialog that comes up, choose Ant->Runtime.
Choose Ant Home Entries (Default) and then choose Add External Jars to add
[Link] from $TOSROOT/tools/java/jars. Ensure that you use the [Link] provided
by TinyOS.

Error:
I get the following error, when I try to access
[Link]

[Link]: Could not initialize class

[Link]

Solution:
The problem comes from the fact that Tomcat is not able to locate the
[Link] file located in the “C:\Program Files\Apache Software
Foundation\Tomcat 6.0\common\classes”. Open the dialog in
Windows>Preferences>Tomcat>JVM and add the above mentioned path in Classpath
textbox.

Error:
When I tried to execute the target, it complains that the any of these packages
[Link]*.* does not exist or
[Link]*.* does not exist or
[Link]*.* does not exist

Solution:
This is because the Eclipse expecting a stubs but could not find that stubs anywhere.
This is most likely because you executed the build target in the wrong order cause
there is some dependencies between them. The correct order is
1. WebNotificationService
2. SensorRepositoryService
3. SensorCollectionService
4. SensorPlanningService

5.6. Building the SensorWeb 2.0 Software - 2

Not only Eclipse and Ant, Tomcat also needs to have access to [Link]. Make sure
you copy this file (the one given by default from TinyOS installation) to
$TOMCAT/webapps/wsrf/WEB-INF/lib where $TOMCAT represents the root
installation of Tomcat. In my machine, it is c:Program Files/Apache Software
Foundation/Tomcat 5.5

Tomcat must also have access to all the jars file inside tinyos-lib. To do this, you can
simply copy all the jar files from tinyos-lib to $TOMCAT/webapps/wsrf/WEB-
INF/lib.

After all the 4 build target is executed successfully, we could check if the services
work by going to their URL. The URL for these services are defined in
[Link] file. Note: change port numbers from 8081 to 8080. Then, visit
these URLs to check that these services work.

Note that you need to start Tomcat to be able to access them.

For example: The URL for the web notification service is

[Link]

To check on their WSDL:

[Link]

In the case where accessing those services shows you an error, it is helpful to debug
Tomcat by making it show more detail log message. To change that, simply open the
file $JAVA_HOME/jre/lib/[Link] and change the global logging level.
The variable is .level and it is INFO by default. Change it to FINE or FINEST.

May want to create a small script which will do everything (or as much as possible)
automatically.

Error:
While running [Link], the GUI loaded up fine but I get the following error
when I tried to use the functionality
AxisFault
faultCode:
{[Link]
faultSubcode:
faultString: [Link]
faultActor:
faultNode:
faultDetail:

{[Link]
tException
at [Link].invoke0(Native Method)
at
[Link](NativeMethodAccessorIm
[Link])
at
[Link](DelegatingMethodAc
[Link])
at [Link]([Link])
at
[Link](RPCProvider.
java:384)
at
[Link](RPCProvider.j
ava:107)
at
[Link]([Link]:
90)
at
[Link](RPCProvide
[Link])
at
[Link]([Link]
)
at
[Link]([Link]
a:32)
at [Link]([Link])
at [Link]([Link])
at
[Link]([Link]
0)
at [Link]([Link])
at
[Link]([Link])
at [Link]([Link])
at
[Link]([Link]
va:327)
 at [Link]([Link])
at
[Link](Applicat
[Link])
at
[Link](ApplicationFilter
[Link])
at
[Link](StandardWrapper
[Link])
at
[Link](StandardContextV
[Link])
at
[Link](StandardHostValve.j
ava:126)
at
[Link]([Link]
va:105)
at
[Link](StandardEngineVal
[Link])
at
[Link]([Link]
:148)
at
[Link]([Link]:
869)
at
[Link].http11.Http11BaseProtocol$Http11ConnectionHandler.
processConnection([Link])
at
[Link](PoolTcpEndp
[Link])
at
[Link](LeaderFoll
[Link])
at
[Link]$[Link](ThreadP
[Link])
at [Link]([Link])
Caused by: [Link]: org/jdom/Element
at
[Link].i
nitialise([Link])
at
[Link]
[Link]([Link])
at
[Link]
eateResource([Link])
... 32 more

{[Link]

[Link]
at
[Link](SOAPFaultBuild
[Link])
at
[Link](SOAPFaultBuil
[Link])
at
[Link](Deserializat
[Link])
at
[Link](Unknown
Source)
at
[Link](
Unknown
Source)
at
[Link]$FragmentC
[Link](Unknown
Source)
at
[Link]
ent(Unknown
Source)
at [Link](Unknown
Source)
at [Link](Unknown
Source)
at [Link](Unknown Source)
at [Link](Unknown
Source)
at [Link]([Link])
at
[Link](DeserializationCo
[Link])
at
[Link]([Link])
at [Link]([Link])
at
[Link](MustUnde
[Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
 at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at
[Link]
[Link]([Link]
:224)
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])

Solution:
The problem lies in this line

Caused by: [Link]: org/jdom/Element

at
[Link](Se
[Link])

You need to ensure that the [Link] file is copied across your $TOMCAT/wsrf/lib
directory.

5.7. Adding Method to Existing WebServices

In order to add a new method to the existing webservices available under SensorWeb
2.0 Softwares (for example SensorPlanningService) you have to follow the steps
mentioned below:
1. Add method signature in SensorPlanningService interface under
“[Link]” package.
e.g,
public Element getSCSLocations() throws ServiceException;

2. Add method implementation in SensorPlanningService class under

“[Link]”
e.g,
public Element getSCSLocations() throws ServiceException {
[Link]("getSCSLocations() --START");
Element element = null;
…
}

3. Next we have to add the method reference in “[Link]”

located in NOSA folder. Since our method is not taking an input parameters
we will have to declare the xsd:type as
<xsd:element name="getSCSLocations" nillable="true">
<xsd:complexType/>
</xsd:element>
4. Now we have to add request and response messages
e.g.
<message name="getSCSLocationsRequest">
<part name="parameters" element="tns:getSCSLocations" />
</message>
<message name="getSCSLocationsResponse">
<part name="parameters" type="tns1:Element" />
</message>

5. Lastly we have to add the operation item.

<operation name="getSCSLocations">
<input message="tns:getSCSLocationsRequest" />
<output message="tns:getSCSLocationsResponse" />
</operation>

6. Replicate these changes in “[Link]” located in

NOSA\schema\SensorPlanningService\SensorPlanningService_instance\

7. Build the SensorWeb 2.0 Software and your changes can be seen in the stubs
generated as a result of build.