Difference between revisions of "Servers"
(→The server configuration file) |
(→entity:arguments) |
||
Line 66: | Line 66: | ||
TBA | TBA | ||
+ | |||
+ | == More information == | ||
+ | |||
+ | You can read more about the configuration and what can you achieve with it in the dedicated section in the [http://cybercore.sourceforge.net/documentation/index.php/The_server_configuration_file CyberCore documentation]. |
Revision as of 08:36, 25 March 2017
Contents
Obtain distribution
There are two ways of obtaining CCIL:
- Download a pre-build zip file, which contains the full system.
- Build from source code.
Download a release
- The releases section in the project's site.
Build from source code
TBA
The server configuration file
In order the server to know which objects to instantiate it has to read the binding from a file. The Turtle format is used, due to its infinite expression abilities.
Location
Within a distribution, it resides in the /config folder, but this can change by specifying the server.config.file option:
-Dserver.config.file=/other/location/config.ttl
The startup scripts for server and application modes differ in this setting.
Format
Below is a sample:
service:sharpfind rdf:type entity:service ; entity:dependsOn service:k-index ; entity:dependsOn service:contexts ; entity:dependsOn service:license ; entity:implementation "com.datacraftmagic.sharpfind.server.SharpFindBackendService" ; entity:classpath "" ; entity:arguments "" .
service:NAME
TBA
rdf:type
Should be:
rdf:type entity:service
entity:dependsOn
TBA
entity:implementation
The class to be instantiated by the Component Container.
entity:classpath
Additional classpath entries. You might want to consider the Class path resolving mechanism in CyberCore about that.
entity:arguments
TBA
More information
You can read more about the configuration and what can you achieve with it in the dedicated section in the CyberCore documentation.