Best Practices for
Developing Extensions for the
vSphere
Client
You can improve
your extension solutions by understanding the process of extending the user
interface layer and service layer of the
vSphere Client ,
and packaging and deploying your extension solutions. Follow best practices to
ensure optimal performance and scalability, and to improve the security of your
vSphere Client
extensions.
Best Practices for Creating Plug-In Packages vSphere Client by creating plug-in modules. Depending on your extension solution, you can extend the user interface layer and the service layer of the vSphere Client . Best Practices for Plug-In Modules Implementation vSphere Web Client extensions. You can then move on to special areas, such as developing HTML-based extension solutions. Best Practices for Developing HTML-Based Extensions vSphere Web Client SDK and the vSphere Client development kit to create HTML-based extensions. Best Practices for Extending the User Interface Layer vSphere Client , follow these best practices. Best Practices for Extending the Service Layer vSphere Web Client service layer, can help you improve the security, scalability, and performance of your extension solutions. Best Practices for SSL Connections Best Practices for Using VimPortType with JAX-WS VimPort connections with the vSphere Web Services SDK. The use of a static VimPort object can alleviate the memory leaks, but can lead to other problems, especially with thread safety. JAX-WS does not provide a thread-safe Port implementation for the VimPort object, which accesses the Web Services API.Best Practices for Deploying and Testing Your vSphere Client Extensions vSphere Client extension, you can follow these recommendations to ensure that your extension is successfully deployed to the vSphere Client .