As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities.

Control Contexts

For any Undertow mod_cluster proxy environment, it is essential to be able to Enable, Disable and Stop a particular Context on a selected worker Node.

It is an equivalent of sending the following MCMP message attributes. Note that the command depends on JVMRoute - for a Node selction and on an Alias - for one of the Aliases a particular Context is configured with.

• Enable context Cmd=ENABLE-APP&Range=CONTEXT&JVMRoute=worker-2&Alias=karm.brq.redhat.com&Context=/clusterbench
• Disable context Cmd=DISABLE-APP&Range=CONTEXT&JVMRoute=worker-2&Alias=karm.brq.redhat.com&Context=/clusterbench
• Stop context Cmd=STOP-APP&Range=CONTEXT&JVMRoute=worker-2&Alias=karm.brq.redhat.com&Context=/clusterbench

Call to action

Enable user to carry out these actions via WildFly CLI.