Difference between revisions of "Running CCIL Applications"
From CCIL
(→Bash) |
(→Java) |
||
| Line 13: | Line 13: | ||
The example fro above translates to: | The example fro above translates to: | ||
<pre> | <pre> | ||
| − | java -cp " | + | java -cp "CCIL_HOME/lib: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 "$@" |
</pre> | </pre> | ||
Where: | Where: | ||
| − | + | ||
* CCIL_HOME - the directory the application is deployed. | * CCIL_HOME - the directory the application is deployed. | ||
* CCIL_CONFIG - the ''ttl'' config file. | * CCIL_CONFIG - the ''ttl'' config file. | ||
[[Passing pipeline arguments from the command line]] | [[Passing pipeline arguments from the command line]] | ||
Latest revision as of 12:20, 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_HOME/lib: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_HOME - the directory the application is deployed.
- CCIL_CONFIG - the ttl config file.
