Error while using existing service layer in HTML5(flex) plugin

[SreeSindhuSruth]

The existing service layer has src and build files(build-java.xml) ,

Added tools folder that has build files .

run the build-plugin-package from ui/tools folder.

Build successful.

When checked in logs, the error is as follows:

c.vmware.vise.vim.directory.extensions.DirectoryExtensionManager  Directory service provider failed while discovering new plugin packages. com.vmware.vise.vim.lookup.LookupServiceConnectionException: vSphere Web Client is missing VMware Lookup Service configuration.
  at com.vmware.vise.vim.lookup.impl.LookupServiceImpl.createLookupService(LookupServiceImpl.java:345)
  at com.vmware.vise.vim.lookup.impl.LookupServiceImpl.createLookupService(LookupServiceImpl.java:326)
  at com.vmware.vise.vim.lookup.impl.LookupServiceImpl.getLookupServiceHolder(LookupServiceImpl.java:304)
  at com.vmware.vise.vim.lookup.impl.LookupServiceImpl.getServiceRegistrationInfos(LookupServiceImpl.java:222)
  at com.vmware.vise.vim.lookup.impl.LookupServiceExtensionManagerProvider.discoverPackagesByEndpointType(LookupServiceExtensionManagerProvider.java:75)
  at com.vmware.vise.vim.lookup.impl.LookupServiceExtensionManagerProvider.discoverPackages(LookupServiceExtensionManagerProvider.java:60)
  at com.vmware.vise.vim.directory.extensions.DirectoryExtensionManager.sessionStarted(DirectoryExtensionManager.java:195)
  at com.vmware.vise.security.spring.DefaultAuthenticationProvider$2.run(DefaultAuthenticationProvider.java:767)
  at com.vmware.vise.util.concurrent.QueuingCachedThreadPool$2.call(QueuingCachedThreadPool.java:571)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at com.vmware.vise.util.concurrent.QueuingCachedThreadPool$QueueProcessor.run(QueuingCachedThreadPool.java:897)
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolEx
ecutor.java:617)
  at java.lang.Thread.run(Thread.java:748)
com.vmware.vise.mvc.telemetry.DataCollectionConfiguratorImpl      Wrong option name. There is no option called VirtualCenter.DataCollector.ConsentData 

[_vladi_]

Hi,

This error log is not related to your plugin in any way so you can safely ignore it.

I assume it is present in the current Fling version. You can try adding ls.url=https://<YOUR_VCENTER_IP>/ls/sdk/ to the webclient.properties file of your local environment to make the error go away.

In any case, this will be sorted out in a follow up release.

Cheers,

Vladi

[SreeSindhuSruth]

The issue is that plugin is not visible in the vCenter.

[_vladi_]

I think the specified error log is not the reason for the plugin issue.

If you are using build-plugin-package you should look for your plugin in your local vSphere Client connected to your vCenter.

In case it is missing there please check if your plugin is present in the local vsphere-ui/plugin-packages/ folder

Check also the local vsphere_client_virgo.log for anything referencing your plugin id. If it is not obvious what goes wrong please provide the log lines related to your plugin deployment so that I can have a look.

Thanks.

Cheers,

Vladi

[SreeSindhuSruth]

Checked the logs it says

java.io.IOException: The bundle at /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/plugin/plugins/service.jar 
should have Bundle-SymbolicName and Bundle-Version headers in its MANIFEST.MF
        at com.vmware.vise.extensionfw.impl.BundleInfoLoader.getBundleInfoFromManifest(BundleInfoLoader.java:163)

I have extracted the jar file and it has Manifest file with bundle-symbolicName and bundle-version.

[_vladi_ · Accepted solution]

This error means that your MANIFEST.MF is either missing, the id or version are missing or it cannot be parsed.

Is your MANIFEST.MF located in the META-INF folder?

Please compare with the MANIFEST.MF of any of the SDK samples and see if there is any syntax that doesn't match. Also make sure your MANIFEST.MF ends with an empty new line (otherwise Virgo might not be able to read your last line).

If this still doesn't work please provide the MANIFEST.MF (ofuscating the proprietary values) so that I can check.

Cheers,

Vladi

[SreeSindhuSruth]

Minor changes for existing and current manifest files. Fixed it.Thanks!