VMware vSphere SDKs and Tools 8.0

8.0 7.0 6.7 6.5

Deploy the Plug-In on a Local
vSphere Client

This procedure describes how you can use the
pickup
 directory to speed up your development process. You can repeat the steps for each new version of the UI and Java service components of your plug-in.
Using the
pickup
 during development is convenient for debugging, but it imposes a performance penalty in production.
  1. Navigate to the
    plugin
     folder where the WAR and JAR files of your plug-in are generated.
    For example, on a Windows machine if you used the default settings of the plug-in generation script, go to
    your_SDK_location
    \html-client-sdk\tools\Plugin generation scripts\plugin-packages\myplugin\plugin
    .
  2. Start the
    vSphere Client
     application server by running the
    startup
     script under
    bin
    .
    For example, on a Windows machine you can find the
    startup
     script at
    your_SDK_location
    \html-client-sdk\vsphere-ui\server\bin
    .
    The string resources are reloaded when you restart the Tomcat server.
  3. Copy JAR files to the
    pickup
     folder on the server. If the JAR files are deployed successfully, copy the WAR files to the same folder.
    For example, on a Windows machine you can paste the files in the
    your_SDK_location
    \html-client-sdk\vsphere-ui\server\pickup
     directory.
    The Tomcat server console is updated when the bundles are deployed on the local
    vSphere Client
    .
  4. Refresh your Web browser at
    https://localhost:9443/ui
     to see the changes.
To complete the verification of your plug-in, deploy the plug-in on a remote
vSphere Client
.

Content feedback and comments