1 |
|
i-scream Server Startup |
2 |
|
======================= |
3 |
|
|
4 |
< |
Current startup sequence: |
4 |
> |
Recommended startup sequence of components: |
5 |
|
|
6 |
< |
uk.ac.ukc.iscream.core.Core |
7 |
< |
uk.ac.ukc.iscream.clientinterface.ClientInterfaceMain |
8 |
< |
uk.ac.ukc.iscream.dbinterface.DBInterfaceMain |
9 |
< |
uk.ac.ukc.iscream.filtermanager.FilterManager |
10 |
< |
uk.ac.ukc.iscream.rootfilter.RootFilterMain |
11 |
< |
uk.ac.ukc.iscream.filter.FilterMain |
6 |
> |
Core |
7 |
> |
ClientInterfaceMain |
8 |
> |
DBInterfaceMain |
9 |
> |
FilterManager |
10 |
> |
RootFilterMain |
11 |
> |
FilterMain |
12 |
|
|
13 |
< |
In it's current state just typing "make run" will compile and package the |
14 |
< |
whole server. However, only the Core can be run from this until the branch |
15 |
< |
is merged back onto the main tree and the ComponentManager integrated. |
13 |
> |
It is not necessary to start both the ClientInterfaceMain and DBInterfaceMain, |
14 |
> |
the server will handle only one. Multiple Filter's can be started as required. |
15 |
> |
|
16 |
> |
These are all loaded through the ComponentManager. More details on how to |
17 |
> |
operate this will be provided later on. Typing "make run" will make an |
18 |
> |
attempt to load it up. |
19 |
|
|
20 |
|
nb. You will need to ensure that the relevant libraries are in the |
21 |
|
build/lib directory. See the README in there for details. |