Manual Registration of Local vSphere Client
You can register your local vSphere Client with the vCenter Server instance using a manual method that applies to either the vCenter Server Appliance or to vCenter Server for Windows.
- Verify that you have access to avCenter Serverinstance.
- Verify that the bash shell is enabled on thevCenter Server Appliance.SeeToggling the vCenter Server Appliance default shell, https://kb.vmware.com/s/article/2100508.
The SDK provides a registration script that you can run in the
vCenter Server
instance. The files generated by this script connect your local Web browser application to the remote vCenter Server
system.- Navigate to thevCenter registration scriptsfolder undertoolsin your SDK installation.
- Copy thedev-setupscript to one of the following locations on thevCenter Serversystem depending on your vSphere deployment.
- On thevCenter Server Appliance, use therootdirectory to copy the script. You must make the file executable.
- On thevCenter Serverfor Windows, use theC:\Users\Administratordirectory to copy the script.
- Run thedev-setupscript in the corresponding directory.The script generates the following files:webclient.properties,store.jks, andds.properties.
- Copy the generated files on your development machine in one of the following locations.On a Windows operating system, you might not be able to see theProgramDatafolder. To change the way items are displayed on a Windows machine, useFolder OptionsfromControl Panel.Operating SystemGenerated FileLocation on Your Development MachineWindowswebclient.propertiesC:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\Mac OS/var/lib/vmware/vsphere-client/vsphere-client/Windowsstore.jksC:\ProgramData\VMware\vCenterServer\cfg\Mac OS/var/lib/vmware/vsphere-client/Windowsds.propertiesC:\ProgramData\VMware\vCenterServer\cfg\vsphere-ui\config\Mac OS/var/lib/vmware/vsphere-client/vsphere-ui/config/
- If you use a Mac OS development environment, edit thewebclient.propertiesfile and set thekeystore.jks.pathproperty to point to the/var/lib/vmware/vsphere-client/store.jksfile.
- If you use a Mac OS development environment, edit theds.propertiesfile and set thesolutionUser.keyStorePathproperty to point to the/var/lib/vmware/vsphere-client/store.jksfile.
- If you use a Mac OS development environment, before you connect your local Web browser application to thevCenter Serversystem for the first time, edit theserver.xmlfile. Change the value of thecertificateKeystoreFileattribute of the<Certificate>element to/var/lib/vmware/vsphere-client/store.jks.You can locate the file at.your_SDK_folder/html-client-sdk/vsphere-ui/server/conf
- Start the localvSphere Clientby running thestartupscript located at thebindirectory of theserverfolder.For example, if you use a Mac OS development environment, the script for starting thevSphere Clientis located at.your_SDK_folder/html-client-sdk/vsphere-ui/server/binYou might need to make the script executable:chmod +x startup.sh
- Open a Web browser and log into your localvSphere Clientathttps://localhost:9443/ui.Your localvSphere Clientconnects to thevCenter Serverinstance and displays the vSphere inventory.
You can deploy your custom plug-ins to the local
vSphere Client
and verify whether the plug-ins function properly in your development environment before deploying them on the remote Web browser applications.