Font size:
commands.properties
Overview
This file contains the metadata describing the commands in the module. Command handlers can be read the file using the following code. Note that the ${module.dir} property will be defined by the command dispatcher.
<property file="${module.dir}/commands.properties"/>
Common
The table below lists the properties defined for any type command
| Property | Description |
|---|---|
| command.name.command-type | Type of handler. Can be either: ant, shell, workflow. ant is the default. |
| command.name.controller | Module name. |
| command.name.daemon | Takes true if daemon, false otherwise. |
| command.name.doc | Description of command. |
Example
command.Stop.command-type=shell command.Stop.controller=Apache command.Stop.daemon=false command.Stop.doc=Stop apache server
Shell type
For commands of the shell type, the following properties are required
| Property | Description |
|---|---|
| command.name.argument-string | Arguments or script code. Used if shell type command handler. |
| command.name.execution-string | Name of program to execute. Used if shell type command handler. |
Example
command.Stop.argument-string=kill `cat ${entity.instance.dir}/httpd.pid`
command.Stop.execution-string=bash
Workflow type
For commandsof the workflow type, the following property is required
| Property | Description |
|---|---|
| command.name.workflow | Comma separated list of commands in the workflow. |
Example
command.Update.command-type=workflow command.Update.workflow=Stop,Package-Install,Configure,Start



