Emulex recently announced support for the new VMware vSphere® 5.1 Web Client with Emulex OneCommand Manager plug-in for VMware vCenter ™ version 1.4.10. So of course, I download the plug-in and replaced my older version. I found out the original OneCommand Manager plug-in for the VMware vCenter desktop client works and installs the same way. But the Web Client is a bit different. I found out I need an extra step to have this puppy working with my Web Client.
My intent in this blog is to inform you of a step that’s different in the configuration process for the plug-in. After trying a few times to get it to appear correctly, I gave in and searched VMware’s documentation. That’s right – I read the manual – in my case. I came across VMware vSphere 5.1 API/SDK Documentation (By default, the plug-in is disabled and does not show up in the Web Client.) When you install the OneCommand Manager plug-in for VMware vCenter version 1.4.10, it will have the plug-in for the Web Client. If you are able to get the plug-in to work through the VMware vCenter desktop client, you should be able to install it for the Web Client. Of course, you must have VMware single sign-on working, the VMware vSphere 5.1 Web Client installed and working, your credentials all taken care off and the correct CIM providers installed to get the plug-in registered and running.
So here’s what we had to do to get the Web Client to appear under “Classic Solutions: for both cluster and host.”
First, the file called webclient.properties in the VMware vSphere Web Client install directory needs to be unhidden, To do that, we need to unhide the %Program Data% directory.
- Open windows explorer
- Select C drive
- Press the alt key to bring up the conventional menu bar
- Click tools
- Click folder options
- Click view
- Check show hidden files, folders and drives
- Click OK
By the way, if you don’t capitalize the ‘P’ in plug-in, the Web Client won’t launch.
To activate the plug-in in the Web Client, a properties file needs to be modified on the server where the vSphere web client is installed.
- Locate the webclient.properties file in theVMware vSphere Web Client install directory, typically %ProgramData%\VMware\vSphere Web Client, and add the following line.
scriptPlugin.enabled = true
- Save and close the file.
- Restart the VMware vSphere Web Client service.
- VMware documentation reference: http://pubs.vmware.com/vsphere-51/topic/com.vmware.wcsdk.pg.doc/LegacyPlugins_Appendix.16.2.html
- Once the above change is made, log back into the Web Client.
- Select Host and Clusters from the Home Tab.
- Open by clicking the right arrow pointing to the name of your VMware vCenter server in the domain to see your cluster and hosts.
- Select the host or the cluster and at the top, you should see a security certificate error. That’s where the plug-in will be registered.
- After registering the plugin, you should now see a tab called “Classic Solutions” for either cluster or Host. See image below.
Can you run both of the plug-ins? Sure! See the image below.