Global Positioning System Reference
In-Depth Information
much more tempting for beginners to find room for improvements. To pro-
vide some ideas, this chapter will include a number of problem statements
for useful additions and features. You should also check the listings in this
chapter with the actual current state of the software at
www.roaf.de
, home
of the ROAF developers.
13.2.1 Setting Up the Environment
The entire distributed application resides in the folders
... \workspace\roaf\ ...
... \workspace\resources\london.roa\client
... \workspace\resources\london.roa\server
The software was developed in the Windows path
D:
n
virtex
, which is hard
coded in different files and needs to be adapted to the environment.
Running the server. Please replace the absolute paths in this batch file to
reflect your environment:
... \london.roa\server\LondonChase.bat
Next, open the server policy file and also adapt the path:
... \london.roa\server\ROServer.policy
For a quick start of server and clients on one PC, the RMI policy is set
to
permissionjava.security.AllPermission
. As soon as clients and server
run on different hardware, the policies should be restricted as described in
the RMI trail. After the two files have been modified, the server software
should be launched from a command line shell with
LondonChase.bat
. If
everything works out, the screen prints the different steps of the server
startup process:
open prop file: ... \ROApp.props
-- listing properties --
:
Created registry on //localhost:1099/
:
allocated registry on //kbeigl-acer:1099/
remoteObject bound to ROserver at 20:55:03 CET 2010
RemoteServer is registered: //kbeigl-acer:1099/ROserver
load osm network file: ... LDN.net.osm
:
mapGraph is setup for navigation.
GameThread was started ...
:
Start waiting for players to register for game ...
At this point, the server is up, running, and waiting for clients to register.
Search WWH ::
Custom Search