It is assumed, that you have installed Gypsy on your system as described in the Runtime Release Installation Guide or the Development Release Installation Guide.

Setting Up a Server and a Basic Runtime Environment

Generate configuration files

Generate and adopt configuration files for all servers (registry, server, home, user) as described in the Configuration section. If you want to see, what's going on in the system set the tracelevel to 1.

Starting the place registry

The Gypsy system needs a place registry for registering places in your local domain. Based on this place registry the agent knows about interesting places to go.

You have to start this service once in your domain by calling:

Unix:

     place-registry -c registry.conf &

Windows:

     start /min place-registry.bat -c registry.conf

There is a tool called place-list which helps you to list the current installed place registry entries.

Examples:

     place-list
     place-list -p rmi://gypsy.infosys.tuwien.ac.at:9500/PlaceRegistry

Starting a Gypsy server

When you have generated and adapted your configuration file you can start a server by calling one of the following examples:

Unix:

     gypsy-server -c myhost.conf &

Windows:

     start /min gypsy-server.bat -c myhost.conf

If you don't provide a configuration file, the server will come up with a default configuration.

You can examine the execution state of the server by looking at the logfile (e.g. myhost.log) in the adm directory.

Starting the home server

Before you can use Gypsy you have to run a home server in your domain. This home server recieves the returning agents and waits for the user frontend to connect and retrieve the returned agents. This is similar to email where your mail waits on a special POP server until your mail reader gets it.

You can start the home-server by calling one of the following examples:

Unix:

     home-server -c yourhomeservername.conf &

Windows:

     start /min home-server.bat -c yourhomeservername.conf

Adding a user to the home server

Each user must have an account at the home server to temporarily store the agents until the user frontend retrieves them. This is normally done by the remote adminstration tool. To simplify the setup for testing Gypsy you can create your account by calling the following command on the same host where the home server is running:

Unix:

     home-admin -a username -p password

Windows:

     home-admin.bat -a username -p password

Starting the user frontend

When you have generated and adapted your configuration file you can start a server by calling one of the following examples:

Unix:

     gypsy -c user.conf

Windows:

     gypsy.bat -c user.conf

You can launch an Hello World! agent, which will visit all places registered with the name Common at the place registry. It will visit all given places and then terminate at the last place on his route.

You can launch an SysInfoCollector agent, which will visit all places registered with the name Common at the place registry. It will return to the home server and wait until you retrieve it by calling the Get Agents menu in the GUI.

The result will be viewed by using a HTML browser (e.g. Netscape). Under Unix the script start-browser connects to a running Netscape (or start Netscape if its not running) to show the result. On Windows a new Netscape is always started. You can change the default browser in the user configuration file.

Stopping the servers

This is normally done by the remote adminstration tool. To the testing of Gypsy, a tool called server-shutdown can be used to terminate a running server.

You can stop a server by calling:

     server-shutdown rmi://myhost:9520/Server-myhost/RMISysadminCommunicator
     server-shutdown -p rmi://myhost.infosys.tuwien.ac.at:9500/PlaceRegistry