Difference between revisions of "Running CCIL applications"
From CCIL
(→Passing pipeline arguments from the command line) |
|||
| Line 28: | Line 28: | ||
* [https://visualvm.github.io/ VisualVM]. | * [https://visualvm.github.io/ VisualVM]. | ||
* [http://openjdk.java.net/tools/svc/jconsole/ JConsole]. | * [http://openjdk.java.net/tools/svc/jconsole/ JConsole]. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 12:19, 7 June 2017
Contents
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.
Monitoring
Just like CyberCore, CCIL exposes all key components as JMX beans, so dedicated applications could be used to monitor its process. Below are some of them:
