| 1 |
|
i-scream Server Package |
| 2 |
|
======================= |
| 3 |
|
|
| 4 |
< |
This package contains the i-scream server. It is currently only tested |
| 5 |
< |
under a Unix-based operating system, but there is no reason why it won't |
| 6 |
< |
work under Windows, or another OS. |
| 4 |
> |
This package contains the i-scream server. It has currently been |
| 5 |
> |
tested on various unix-based operating systems, and experimentally |
| 6 |
> |
tested on windows. There is, however, no reason for it to operate |
| 7 |
> |
differently on any platform, as it's all Java based. |
| 8 |
|
|
| 9 |
< |
The iscream.jar file contains all the server code, and can be started up |
| 10 |
< |
by running the run.sh script. More details will be provided later on how |
| 11 |
< |
to start this up when details are finalised. |
| 9 |
> |
The iscream-server.jar file contains all the server code, and can |
| 10 |
> |
be started up by running the run.sh script. The etc/default.properties |
| 11 |
> |
file specifies the components to start, and their order. |
| 12 |
|
|
| 13 |
< |
You must ensure that the JacORB and XML libraries are in the lib |
| 14 |
< |
directory. The README in lib will explain how to acquire these files. |
| 13 |
> |
You must ensure that the relevant libraries are in the lib directory, |
| 14 |
> |
although if you have the compiled server package these files will |
| 15 |
> |
already be present. The README in lib will explain how to acquire |
| 16 |
> |
these files if they are not available. |
| 17 |
|
|
| 18 |
< |
Finally, the etc directory contains the default configuration files. These |
| 19 |
< |
can be expanded as required. See the configuration documentation for |
| 20 |
< |
further details. |
| 18 |
< |
|
| 18 |
> |
Finally, the etc directory contains some default configuration |
| 19 |
> |
files. These can be expanded as required. See the server user guide |
| 20 |
> |
documentation for further details. |
