Handling Actions for HTML-Based Action Extensions

When you create an HTML-based action extension to the vSphere Client, you must create an actions controller class on the Tomcat server to respond to the REST API requests from the client code.

A best practice is to implement the controller class as a simple dispatcher that maps the action UIDs to Java services. You can invoke custom services or translate REST API requests to Data Manager requests.

Example Java Actions Controller Class

...
/**
  * Perform headless action on a VirtualMachine vSphere object.
  */
   @RequestMapping( value="vm-headless-action",
                    method = RequestMethod.POST)
   @ResponseBody
public void vmHeadlessAction() {
   // Implement your logic here to trigger an action on a virtual machine.
            }
...