Difference between revisions of "Running CCIL applications"
From CCIL
| (2 intermediate revisions by the same user not shown) | |||
| Line 22: | Line 22: | ||
* CCIL_CONFIG - the ''ttl'' config file. | * CCIL_CONFIG - the ''ttl'' config file. | ||
| − | [[ | + | == Monitoring == |
| + | |||
| + | Just like [http://cybercore.sourceforge.net CyberCore], ''CCIL'' exposes all key components as [https://en.wikipedia.org/wiki/Java_Management_Extensions JMX] beans, so dedicated applications could be used to monitor its process. | ||
| + | Below are some of them: | ||
| + | * [https://visualvm.github.io/ VisualVM]. | ||
| + | * [http://openjdk.java.net/tools/svc/jconsole/ JConsole]. | ||
| + | |||
| + | == See also == | ||
| + | * [[How to provide parameter values from the command line?]] | ||
Latest revision as of 12:26, 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:
