next up previous contents
Next: Plain Socket (PLS) Communication Up: RMI Communication Service Previous: Structure and exported Objects   Contents

Configuration Options

In the section of the configuration file for the RMICommService, [tagents.sysagent.communication.rmi.RMICommService], there are three options at this moment recognized by the RMICommService:

PORT
The built - in RMI registry can use a different port for the registry to listen on. The standard port is 1099 but you can choose every port number which is free on your machine.
MAFFINDER
Defines the mode of the RMIMAFFinderServiceProxy. Valid options are:

REAL
There is a real MAFFinder running on this machine, so the RMIMAFFinderServiceProxy is run in ``wrapper'' mode which means it is exported to the RMI registry and listen to calls to the real MAFFinder from outside.
PROXY
If the RMIMAFFinderServiceProxy runs as proxy it forwards all local calls to the MAFFinder through the wrapper to the real MAFFinder on another machine. In this mode the RMIMAFFinderServiceProxy is exported to the System to let Agents use it to do calls to the MAFFinder. If using this modus you have to give the MAFFINDER_LOCATION all other modus do not require it.
NO
If the RMICommService should not use the RMIMAFFinderServiceProxy at all. Could be used because there is already one protocol available for accessing the MAFFinder.
MAFFINDER_LOCATION
The location of the wrapper to the real MAFFinder. It is an URL used to connect to the wrapper over RMI. It has the form rmi://ip_number_of_host[:port]/MAFFinder. If you use a different port as the standard port for the RMI registry one should give here the port of the RMI registry of the machine where the MAFFinder resides. To keep the form in a standard way it is recommended to give always the port. The protocol is of course rmi and the name of the object is ``MAFFinder'' as described in the former section about the RMI naming conventions in TAgents.


next up previous contents
Next: Plain Socket (PLS) Communication Up: RMI Communication Service Previous: Structure and exported Objects   Contents
Thomas Letsch 2001-02-21