![]() In this release of the Fling there is more manual configuration that is done on the Windows side, but this will be more automated in a future release of the Fling. The process is similar to the vCenter Server Appliance. Finally, the registration script is starting the web server, also installing any packages and plugins needed.Īs stated earlier the vSphere HTML5 Web Client Fling also works with vCenter 6.0 for Windows. Making sure the vCenter Server Appliance bash shell is enabled allows for SCP to copy these configuration files over to the Fling Appliance. etc/init.d/vsphere-client configure -start yes -user root -vc -ntp Ĭontinue the registration process by answering “Yes” to continue connecting and entering your vCenter Server Appliance password.ĭuring the registration process the following configuration files are created and copied from the vCenter Server Appliance to the vSphere HTML5 Web Client Fling: webclient.properties, ds.properties, and store.jks. Run the following command to register the Fling appliance with vCenter Server Appliance: Let’s go through the process of configuring the vSphere HTML5 Web Client Fling with both the vCenter Server Appliance and vCenter for Windows Configuration with the vCenter Server Appliance ![]() This is taken care of for you when using the vSphere Web Client. Note: when deploying with the vSphere client (aka C# or Thick client) an IP pool is required. When the Fling appliance is at the console screen, SSH using the login username root and password demova. Go through the deploy OVF Template wizard, power on the the fling appliance and wait for the boot process to complete. The Fling OVF can be deployed using either the vSphere 6.0 Web Client or Embedded Host Client. ![]() Prior to deploying the vSphere HTML5 web client Fling appliance verify all specifications are in place and prerequisites have been met. VSphere HTML5 Web Client Fling Deployment
0 Comments
Leave a Reply. |