Home

Search

COMMON INTRODUCTION

GYPSY

DOCUMENTATION

DEVELOPMENT

DISTRIBUTION

  • Software Requirements
  • Package Distribution
  • CVS Distribution
  • Building the package

  • Runtime Installation
  • Development Installation
  • Configuration
  • Getting Started

    Contact us


  • DSG Logo

    Gypsy Configuration



    This page provides you help for setting up your Gypsy configuration files for the various servers.

    Generating Configuration Files

    To enable an easier setup of servers, we've provided a program which generates the most common used configuration settings:

    gypsy-config -h
    lists all available options.

    vmprop-list -d
    lists all default settings.

    Here is an example setup for a server running on myhost.mydomain:
    gypsy-config --server myhost
    generates a file called myhost.conf in the $GYPSY_ROOT/adm directory. This file is typical for basic agent servers in the system.

    Now you have to provide a password to administer (e.g. shutdown) this server:
    gypsy-passwd -c myhost.conf
    The password is added encrypted to the configuration file.


    Changing the Default Configuration Settings

    All default configuration settings are in the
    $GYPSY_ROOT/at/ac/tuwien/infosys/gypsy/server/GypsyConfig.java
    file and can be changed there. Don't forget to recompile the project!

    For most site-specific settings it would be sufficient to change the
    $GYPSY_ROOT/at/ac/tuwien/infosys/gypsy/server/GenerateConfig.java
    file and recompile the project.


    Configuration Entries

    KeyDescription of Associated Value
    gypsy.classloader.cache.flushThe classloader writes new loaded classes immediately into the jar-archive or directory instead of holding it in the main memory.
    gypsy.classloader.cache.inventory.externalIf true the inventory file of the classloader cache is hold in an external ASCII file instead of putting it into the cache archive.
    gypsy.classloader.cache.inventory.filenameThe name of the external inventory file.
    gypsy.classloader.cache.jarIf true the cache is a jar file otherwise a directory.
    gypsy.classloader.cache.jar.filenameThe name of the classloader cache file.
    gypsy.classloader.cache.pathThe path to the cachefile/inventory file or the cache directory if no cache filename is given.
    gypsy.classloader.cache.sizeThe size in KB of all compressed entries in the classloader cache.
    gypsy.classloader.codebase.fileA file containing all allowed classloader codebase URLs for this server.
    gypsy.codebaseThe default codebase for agents.
    gypsy.domain.admin.emailThe email address of the local domain administrator.
    gypsy.domain.nameThe local domainname where this server is located in case a full qualified hostname cannot be determined.
    gypsy.placeregistry.uriThe URL for the local (or a valid) place registry.
    gypsy.server.communicator.emailThe address for the local email communicator.
    gypsy.server.communicator.passwordThe email communicators password for the local POP server. This is just a workaround until the remote administration tool exists.
    gypsy.server.communicator.pophostThe POP server where the email communicator can get incoming agents.
    gypsy.server.communicator.rmiportThe Java RMI registry port for RMI communicators.
    gypsy.server.log.databaseJDBC database connection string for a cetralized log server in a domain.
    gypsy.server.log.dbserverThe RMI URI for the centralized log server of a domain.
    gypsy.server.log.dbserver.enabledIf true the local server formwards the incoming LogMessengers to a centralized log server in a domain.
    gypsy.server.log.file.enabledIf true the server logs to the given filename otherwise the log messages will be printed to the system console.
    gypsy.server.log.fileThe path/filename for log messages.
    gypsy.server.nameThe name of this server.
    gypsy.server.passwordEncrypted password for this server.
    gypsy.server.security.filenameThe name of the security configuration file of this server.
    gypsy.tracelevelThe tracelevel for this server. It must be in a range between 0:3 - 0 ... trace nothing, 3 ... trace everything.
    gypsy.user.emailThe email address of the user to send status messages.
    gypsy.user.email.notifyIf true the user requests to be notified if the agent returns home.
    gypsy.user.fullnameThe full name of the user.
    gypsy.user.home.loginnameThe loginname at the homeserver. This must be a vaild username at the homeserver otherwise agents cannot return.
    gypsy.user.home.sysuriThe URL for the user communicator on the home server. The user gets status messages and request returned agents on this URL.
    gypsy.user.home.uriThe URL for the agent communicator on the home server. Agents which have finished their task return home to this URL.
    gypsy.user.htmlbrowserThe favorite HTML browser to view the results of returning agents.
    gypsy.user.result.pathThe directory where the results of returning agents are written as HTML file.
    gypsy.user.sms.emailThe SMS email gateway address of the agent's owner.
    gypsy.user.sms.keyThe Subject key for SMS messages. Some provider (e.g. in Austria max.mobil) require this to send valid SMS messages over the email gateway.
    gypsy.user.sms.notifyIf true the user requests the agent to notify him if he returns home.
    mail.smtp.hostThe local SMTP server for outgoing emails.

    accesses to this page since January 1, 1999;
    © 1997-2000 Distributed Systems Group , Technical University of Vienna .
    Created and maintained by Wolfgang Lugmayr ( W.Lugmayr@infosys.tuwien.ac.at ).

    Last update: Tue Jan 4 15:49:19 CET 2000 .