Normally you will not need to change the configuration file to follow this tutorial. However sometimes this is necessary to fit in with your system.
By default, the SGS server will run under port 9092. If this is not
acceptable to you for any reason, you can change this in the configuration file.
Look at the config file provided with the JStyx distribution (SGSconfig.xml).
Before the part that contains the details of all the services, there is a section
for configuring the server:
<server port="9092"></server>
Simply change the port number in this section to the number of your choice (the range of port numbers that you are allowed to choose is system-dependent).
Note that the SGS server only runs under a single port. Therefore, this is the only port that you will need to open through any firewalls that the server happens to lie behind. SGS clients need no incoming ports open: they simply need to be able to make an outgoing connection to the server.
While a Styx Grid Service is running, it creates a number of files on the
server's hard disk. These files are mostly cached copies of the input and
output files. By default, these files are kept in a directory called
StyxGridServices in the home directory of the user that is
running the SGS server (this is detected through Java's user.home
system property. Under Unix-type systems this will be $HOME
and under Windows it will be C:\Documents and Settings\username.)
If you would prefer these cached files to be kept elsewhere you can set this in the configuration file, for example:
<server port="9092" cacheLocation="/usr/local/sgs/cache"></server>
The cacheLocation must be a directory. If it does not already
exist it will be created. You must make sure that the user that is running the
SGS server has write permissions in this directory.
(For developers only, really.) The logging behaviour of the system is
controlled by the log4j.properties file in the conf
directory of the distribution. To see debug messages for a particular class,
change the logging level of that class to DEBUG. You can see the individual
Styx messages that are exchanged between client and server by setting the
logging levels of the StyxServerProtocolHandler and StyxConnection to
DEBUG. This is not recommended for normal use as it will significantly slow
the system down.
