If you want to verify your custom plug-ins, you can deploy the plug-ins first on your local vSphere Client and vSphere Web Client. You must register your local instances of the Web browser applications with the vCenter Server Appliance or vCenter Server for Windows to be able to deploy your plug-ins locally.

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.

Prerequisites

■

Verify that you have access to a vCenter Server instance.

Procedure
1

Navigate to the vCenter registration scripts folder under tools in your SDK installation.

2

Copy the dev-setup script to one of the following locations on the vCenter Server system depending on your vSphere deployment.

■

On the vCenter Server Appliance, use the root directory to copy the script. You must make the file executable.

■

On the vCenter Server for Windows, use the C:\Users\Administrator directory to copy the script.

3

Run the dev-setup script in the corresponding directory.

The script generates the following files: webclient.properties, store.jks, and ds.properties.

4

Copy the generated files on your development machine in one of the following locations.

Note

On a Windows operating system, you might not be able to see the ProgramData folder. To change the way items are displayed on a Windows machine, use Folder Options from Control Panel.

Operating System

Generated File

Location on Your Development Machine

Windows

webclient.properties

C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\

Mac OS

/var/lib/vmware/vsphere-client/vsphere-client/

Windows

store.jks

C:\ProgramData\VMware\vCenterServer\cfg\

Mac OS

/var/lib/vmware/vsphere-client/

Windows

ds.properties

C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\config\

Mac OS

/var/lib/vmware/vsphere-client/vsphere-client/config/

5

Set up the VMWARE_CFG_DIR environment variable on your local machine to point to one of the following directories:

■

For a Windows development environment, set C:\ProgramData\VMware\vCenterServer\cfg\ as a value to the variable.

■

For a Mac OS development environment, set /var/lib/vmware/vsphere-client or /var/lib/vmware/vsphere-ui as a value to the variable.

6

If you use a Mac OS development environment, edit the following properties to point to the /var/lib/vmware/vsphere-client/store.jks file.

a

In the webclient.properties file, edit the keystore.jks.path property.

b

In the ds.properties file, edit the solutionUser.keyStorePath property.

7

If you use a Mac OS development environment, before you connect your local Web browser application to the vCenter Server system for the first time, edit the tomcat-server.xml file. Add the /var/lib/vmware/vsphere-client/store.jks value to the keystoreFile.

You can locate the file at your_SDK_folder/vsphere-client-sdk/html-client-sdk/vsphere-ui/server/configuration or your_SDK_folder/vsphere-client-sdk/flex-client-sdk/vsphere-client/server/configuration depending on the Web browser application.

8

Start the local vSphere Client or vSphere Web Client by running the startup script located at the bin directory of the server folder.

For example, if you use a Mac OS development environment, the script for starting the vSphere Client is located at your_SDK_folder\vsphere-client-sdk\html-client-sdk\vsphere-ui\server\bin.

9

Open a Web browser and log into your local vSphere Client at https://localhost:9443/ui or into your local vSphere Web Client at https://localhost:9443/vsphere-client.

Your local vSphere Client or vSphere Web Client connects to the vCenter Server instance and displays the vSphere inventory.

What to do next

You can deploy your custom plug-ins to the local vSphere Client or vSphere Web Client and verify whether the plug-ins function properly in your development environment before deploying them on the remote Web browser applications.

Previous topic: Install the vSphere Web Client Tools Eclipse Plug-In
Next topic: Configure the Virgo Server in Your Eclipse IDE