VMware vSphere

 View Only
  • 1.  Correct HTML Console SDK destination URL

    Posted Oct 21, 2015 05:48 PM

    Hello all,

    I'm looking at building a simple demo application using the HTML Console SDK‌‌ to connect to remote vm's on ESXI. The programming guide I'm using is here: https://www.vmware.com/support/developer/html-console/html-console-sdk-100-programmer-guide.pdf .

    My question is finding the appropriate destination url, as seen on page 5, in the 6th step. I've downloaded the sdk files and have everything setup and running locally on Tomcat. I've looked through the documentation extensively as well as online to find a more detailed explanation for the connection url to use but cannot find one. Their documentation is using websockets to make the connection but the url is just to the local machine.

    Has anyone had any experience with this and would be able to provide some feedback? Does anyone know how to find the destination url of a vm on the server?



  • 2.  RE: Correct HTML Console SDK destination URL

    Posted Apr 06, 2016 09:19 AM

    Even i am looking for same solution.  



  • 3.  RE: Correct HTML Console SDK destination URL

    Posted Apr 06, 2016 10:48 PM

    ‌i use powercli to build the console URL for a projeat I work on. I grab a few items from powercli and throw that in a DB which My WebApp can then pull the url and display that to our users.

    LEt me know if powercli is a viable option and I can point you in the right direction.



  • 4.  RE: Correct HTML Console SDK destination URL
    Best Answer

    Posted Jul 27, 2017 03:26 PM

    Update on this topic. I have been able to generate a MKS ticket and can connect to virtual machines.

    The correct format is: <ws | wss> :// <host:port>/ <path> /? <authentication info>.

    An example of a working connection for me is: wss://10.10.28.14:443/ticket/735e1558857b363b.

    Hope this helps some of you out.



  • 5.  RE: Correct HTML Console SDK destination URL

    Posted Jan 09, 2024 06:35 PM

    I tried 

        wmks.connect("wss://myIP:902/ticket/52866e46-55f7-6b0a-7680-54d3edd1d73a");
    and 
     
        wmks.connect("wss://myIP:443/ticket/52866e46-55f7-6b0a-7680-54d3edd1d73a");
     
     
    wmks.min.js:1 WebSocket connection to 'wss://myIP/ticket/52866e46-55f7-6b0a-7680-54d3edd1d73a' failed: