The environment names will be used on the command line, so make them short, meaningful, and command-line-friendly. The jkUrl values are the most important, and they should work in your browser (without any authentication, for now). Note that the trailing slash may be important, depending on your Apache config.
Query a set of hosts defined for the given environment and output the status of each configured Tomcat node/worker.
The <env> value you specify must be defined in your jkmod.json file in the current working directory.
$ jkmod list <env>
Update the activation status for given Tomcat node/worker in the given environment.
The <env> value you specify must be defined in your jkmod.json file in the current working directory.
The <tomcatHost> value should come from the output of jkmod list <env>.
The <status> value should be one of:
ACT for active (the node/worker will receive traffic from the Apache load balancer pool)
DIS for disabled (the node/worker will only receive sticky traffic from existing sessions - meant to bleed traffic off of this worker)
STP for stopped (the node/worker will stop receiving any traffic)
$ jkmod edit <env> <tomcatHost> <status>
For questions about the load balancer member status, see the mod_jk documentation.