Difference between revisions of "Running CCIL Applications"
From CCIL
(Created page with " == Syntax == Usually, all distributions come with pre-defined script files which deliver the magic. For instance, if you use the ''DCMPC Dictionary'' distribution, you would...") |
(→Bash) |
||
Line 6: | Line 6: | ||
=== Bash === | === Bash === | ||
<pre> | <pre> | ||
− | ./dcmpc-dictionary-app fill | + | ./dcmpc-dictionary-app dictionary fill |
</pre> | </pre> | ||
+ | This instruction will start CCIL in application mode and execute the ''fill'' pipeline of the ''dictionary'' context. | ||
=== Java === | === Java === |
Revision as of 10:39, 13 May 2017
Syntax
Usually, all distributions come with pre-defined script files which deliver the magic. For instance, if you use the DCMPC Dictionary distribution, you would go to the /bin folder and simply type:
Bash
./dcmpc-dictionary-app dictionary fill
This instruction will start CCIL in application mode and execute the fill pipeline of the dictionary context.
Java
The example fro above translates to:
java -cp "CCIL_CLASSPATH:CCIL_HOME/config:CCIL_HOME/launcher/*" -Dserver.config.file=CCIL_CONFIG -Dserver.home.dir=$CCIL_HOME -Xmx1024M -Dserver.context.dir=$CCIL_CONTEXT -Dserver.jmx.enabled=false net.ccil.execution.CcilConsoleApp -execute -root $CCIL_HOME/context/apps "$@"
Where:
- CCIL_CLASSPATH - The library jars which form the application's execution code. In a distribution, this is the content of the lib folder.
- CCIL_HOME - the directory the application is deployed.
- CCIL_CONFIG - the ttl config file.