stoevm's Posts

Hi aparajirSG, This is not the correct sub-forum for your query. Please try posting your question to the vSphere-Management-SDK sub-forum https://communities.vmware.com/t5/vSphere-Management-SDK/bd-p/4524. Thanks, Martin

Hi kumartade, Currently there is no support to dynamically show/hide a summary view.  Can you share more information on the use-case why this is needed. This might help us to define this as a feature request on our side. Thanks

On second thought as the error has caused by: Unable to resolve /C:/vsphere-client-sdk-7.0.0.10100-15863815/html-client-sdk/vsphere-ui/plugin-packages/vnsui/com.hpe.vnsui-1.1.15.esa/vns-service.jar: missing requirement org.apache.aries.subsystem.core.archive.ImportPackageRequirement: namespace=osgi.wiring.package, attributes={}, directives={filter=(&(osgi.wiring.package=com.vmware.o11n.sdk.rest.client.impl)(version>=0.0.0)), resolution=mandatory}, resource=/C:/vsphere-client-sdk-7.0.0.10100-15863815/html-client-sdk/vsphere-ui/plugin-packages/vnsui/com.hpe.vnsui-1.1.15.esa/vns-service.jar I think that the com.vmware.o11n.sdk.rest.client.impl   might be missing from the jar manifest file. Martin.

Hi, As the error says: com.hpe.vnsui.nskVolume is missing from the manifest of the war service. Please take a look and fix the missing packages from the manifest of the war and jar services as well.

Hi AnoopHPE,  Why do you want to register 7.0 vSphere Client SDK to a 6.7 vCenter ?  Also about the errors, you can try to resolve it by creating the missing files:  C:\ProgramData\VMware\vCenterServer\cfg\vsphereFeatures\vsphereFeatures.cfg C:/ProgramData/VMware/vCenterServer/cfg/\vsphereFeatures\techPreview.cfg If there are additiona errors after this, please share them with us. Martin

Hi abby,  Can you elaborate on what do you mean by cluster level plugin registration ?  On a side note, the cluster extensions are shown for supervisor clusters as well, which means that if you had a view for a cluster, that view will be shown for supervisor cluster as well. Best, Martin

Hi Yang, There has been a small change in the architecture in the vSphere Client navigations in 7.0. I tested on a 7.0 environment the following scenario and it worked: 1) opened a plugin view 2) from the developers console executed snipped similar to this   window.frameElement.htmlClientSdk.app.navigateTo({       targetViewId: 'com.xxxxxxx.summary',       objectId: objectId,       customData: ['a', 'b', 'c']     }); 3) when the new view loaded I validated that the getNavigationData returns ['a', 'b', 'c'] and the getContextObjects()[0] returned the object to which I navigated. Can you share the steps on how can I reproduce the scenario when the  GET navigation request does not have an objectId ? Namely this one: request URL: https://ssssssss/ui/navigation/leaf/com.xxxxxxx.summary  Also can you share information about the vCenter Server, what build number is it ? Thanks, Martin

Hi Yang, Are you trying to get the objectId of the previously selected object, namely the object from which the navigation was triggered or you are trying to get the selectedTargets ? I just verified that after the navigateTo Api has been called and the navigation executed, the getContextObjects API returns the correct object. Also there is a format error in the json you provided to the navigateTo API. The customData value is not a valid json  { objectId, selectedTarget }. On a side note: The Refresh/Next Page/Back Page clears the navigation data as this is not considered correct navigation (namely it is not done with the usage of navigateTo API).   Martin

Hi Kobi, A version of an SDK sample will be available in a future release where the Task creation is demonstrated in details. Keeping this in mind I tried to reproduce the scenario described in this communication but I did not succeed . I tryed with task keys like `com.infinidat.powertools.develop.host.ci012.expose_infinidat_snapshot` but did not succeed to break it. Few things to have in mind, which were new to me as well: 1) The vSphere Client downloads new catalogs in ...\vsphere-client\cmCatalog on startup, meaning that the sequence of testing the tasks localization is as follows:     - stop the vSphere Client     - register the plug-in.     - start the vSphere Client 2) The vSphere Client caches the catalogs, namely after the plugin has been registered with an update on the localization strings for the tasks,        the catalogs must be deleted from ...\vsphere-client\cmCatalog. 3) The creation of the task is done with some_task_id, and the localization strings are created with some_task_id.label and some_task_id.summary (just writing it here I know that this is known info.) If you can create a simple reproducable version of the SDK html-sample, which I can deploy in our test environments and verify, I will be more than happy to test it out and root cause the problem. Best, Martin.

Hi wodge,   Thanks for reporting this issue, This is a known limitation for rendering html content in the flash client. Since the Flex Client is depricated, there are technical limitations and this issue can not be fixed. The H5 Client is going to be the focus point in the next releases.   Best, Martin

Hi abby21,   Just looking at the exception, we could not determine what the root cause might be. If you can reproduce this with an existing sample of the SDK, we will be glad to help,  but I think it will be more useful to post this question in the VI Java forum.   Best, Martin

Hi CathyBr, Thanks for raising this again,Together with some internal teams in VMware we narrowed down the problem and fixed it. This fix should be available in an upcoming release. Thanks, Martin

The directory where you want your migration file to be created must exist.   meaning that the value of the migrationFile argument should be some directory already present on the file system + 'filename'.   Best, Martin