how rhev-m talks to vdsm ?

Hi,

Can somebody help me understand how the command flow (say for VM shutdown) is from "web browser" of  rhev-m to vdsm of the hypervisor ?

Is it

web browser --> Java App --> REST-API --> TCP -54321 --> vdsm --> libvirt ??

When RHEV mentions RHEV-API, does it refer to REST API only ?