CommandLine Mode

Home > Books > Adminstrator's Guide to NetKernel > Deployment > CommandLine Mode

The 1060 NetKernel may be run as a command line resource processor. It can be invoked with the dexter shell script found in the [install]/bin directory, which uses the com.ten60.netkernel.cli.CommandLine class in the 1060netkernel-cli.jar.

Commandline Switches

Command Line processing supports several options.

Switch	Description
-b <basepath>	Set the installation basepath from where kernel resources will be located. The dexter script is configured to use the installation directory by default.
-u <uri>	uri to request. CWU is the current working directory by default unless overridden with -x.
-P <param>	Parameter literal. An in-line literal to pass as a parameter
-x	Do NOT Export Current Working URI, use absolute idocuri as working URI
-v	Verbose output
-s	Get Parameter from Stdin, overrides -p -P, gives piped execution

Performance

Command-line invocation is provided as a convenience. It is expensive to boot the kernel just to execute a command-line process. If used in this mode it is better to create batch processing files in the NetKernel-domain than the shell-domain since the former only requires one boot of the kernel to process many files whereas the latter requires a boot for each file.

Boot time can be improved by removing unnecessary modules from the deployed modules, especially transport fulcrums.

An alternative approach to using the Command-line mode is to run the NetKernel as a server and to invoke it from a console client on the HTTP transport. It is also straight-forward to add a new transport to handle a command-line protocol for a thin command-line client.