Hello everyone, VMware is conducting our annual Developer Survey and we want to hear from YOU so we can assess and improve our developer program to better serve your needs. PLUS, we will be giving away a new Sonos Move smart speaker to one lucky participant! To take the survey, visit the link below:

http://www.vmware.com/go/developer-survey-2019

Thank you!

Hi,

We are using new JS APIs SDK(local) of vSphere 6.5U2 SDK for our plugin. We had implemented two portlets on datastore object. But global refresh is not working as it is working on global views.

We are going through our implementation. But no clue what's wrong.

Can some one from VMware team confirm the following query:

Is Global refresh supported vSphere entity(say Datastore) Summary portlet is supported?

Are there any limitations?

Regards,

Kumar

Hi Team,

Im trying to define and action extension without title and close button on plugin.xml by not specifying the dialogTitle tag.

But it is adding padding and close button(highlighted in red color) as shown below:

Result:

Expectation:

Sample extension code Snippet:

<extension id="com.acme.myhtmlplugin.datastore.provisioning.actions">

        <extendedPoint>vise.actions.sets</extendedPoint>

        <object>

            <actions>

                <com.vmware.actionsfw.ActionSpec>

                    <uid>com.acme.myhtmlplugin.provisionDatastore</uid>

                    <label>#{DatastoreProvision.action.label}</label>

                    <delegate>

                        <className>com.vmware.vsphere.client.HtmlPluginModalAction</className>

                        <object>

                            <root>

                                <actionUrl>/ui/myhtmlplugin/index.html?view=datastore-provisioning</actionUrl> //No DialogTitle

                                <dialogSize>1152,455</dialogSize>

                            </root>

                        </object>

                    </delegate>

                </com.vmware.actionsfw.ActionSpec>

            </actions>

        </object>

        <metadata>

            <objectType>Datacenter,ClusterComputeResource,HostSystem</objectType>

        </metadata>

    </extension>

I could achieve the desired behavior using API programmatically by passing title=null and closable=false in modal config.

How to achieve the same thing in plugin.xml ?

SDK Details:

vSphere SDK: using vSphere New JS 6.5U2 SDK.

Thanks,

Kumar

Hi  _vladi_,laurentsd, Denis_Chorbadzhiyski, Daryll, Kris

Is there any option to add the Action/Link/Button as specified in the screenshot?

In this space, once we click on Action/Link/Button display the modal dialog and add the system.

And the added system should be displayed under the list in More object.

As this workflow seems to proper for our plugin.

Can you please suggest?

Thanks,

Sujeet Kalaskar

In one of our vCenter's UserSessionService serviceUrl does not provide the port details...

What we expect is serviceUrl to be "https://<IP>:<Port>/sdk". Port mostly is 443. But what we get is "https://<IP>/sdk" (Just IP without port). We have written some code based on the port number. Any idea why would this happen. I have set up and if needed I can provide more details/ logs.

Hi _vladi_

I wanted to add the navigation from one view to other.

Example: Similar to Breadcrumb, where we can navigate to is parent node by clicking the link(href)

Home->Host->Controller->Logical

Logical is my current view, whenever I click on the Home link it should navigate to "vsphere.core.controlcenter.domainView".

Similarly for the Host "com.xxx.xxx.host" and "com.xxx.xxx.controller".

I tried using the below code, on click on "Home" link callHome() function is called

targetViewID is "vsphere.core.controlcenter.domainView"

what will be the object ID, when navigating to "vsphere.core.controlcenter.domainView"?

callHome(){

     const navConfig = new NavConfig("vsphere.core.controlcenter.domainView", "");

     this.gs.getClientSdk().app.navigateTo(navConfig);

}

I need some clarification of targetViewID and ObjectID.

targetViewID -> The view which we want to display?

ObjectID -> It should be the current page object ID or targetView's object ID?

Thanks,

Sujeet Kalaskar

Hi _vladi_,

I am unable to view/see the navigation between previously visited views as shown in below screenshot.

Whether this option is deprecated or we need to add any specific extension point for it?

Can you please help?

Thanks

Sujeet Kalaskar

If Windows 7/10 VMs are being hosted by VMWare, is there any way to force all existing applications running on Windows to use VMCI sockets instead of the Windows' socket library?  Want to speed up network communication between VM hosts.

Hello,
I have a vSphere plugin created a while ago.
It works fine except for the tasks' labels in the 'Tasks' window and the 'Recent Tasks' frame.
All of its tasks are shown as <task-name>.label and not as the actual tasks' names.
It happens in both web clients (flex and html 5) for all tested vSphere versions (6.0, 6.5, 6.7u1).
It is worth mentioning we've seen cases in which our plugin's tasks are shown correctly and it seems to be non consistent.

I went through the web and read many discussions of people who had similar issues but non of the suggested solusions worked for me:

https://communities.vmware.com/thread/513423 is the closest description of my problem.
I followed Peter Ivanov's instructions (on vSphere 6.7u1).
My plugin is not shown in /etc/vmware/vsphere-client/cmCatalog or /etc/vmware/vsphere-ui/cmCatalog/

I entered https://<vc-ip>/cm/mob/?moid=ServiceManager and searched the suggested xml criteria. My plugin did not show there.

service-control --status result is:
Stopped:
 vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-vcha vsan-dps
Running:
 applmgmt lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rhttpproxy vmware-sca vmware-sps vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui

my plugin is called powertools.
vsphere_client_virgo.log is attached.

What am I missing?
I'm willing to provide any required additional information.

Hi all,

The Upgrading Your Plug-in To Maintain Compatibility with vSphere 6.7 document has been updated.

Plugin writers who have not migrated to support 6.7 yet can now make use of a simpler approach to do that - it is listed as Option 1 on page 4.

Cheers,

Vladi

Hi Team,

I'm trying to build remote plugin sample bundled as part of vsphere-client-sdk-6.7.0.40000-14186396.

Following are the outputs for mvn validate

C:\Users\kumart\Downloads\vsphere-client-sdk-6.7.0.40000-14186396\html-client-sdk\samples\remote-plugin-sample

λ mvn vaidate -e

[INFO] Error stacktraces are turned on.

[INFO] Scanning for projects...

[WARNING]

[WARNING] Some problems were encountered while building the effective model for com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT

[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 263, column 18

[WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ line 174, column 18

[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 247, column 18

[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-install-plugin is missing. @ line 131, column 18

[WARNING]

[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.

[WARNING]

[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.

[WARNING]

[INFO]

[INFO] --------------< com.vmware.samples:remote-plugin-sample >---------------

[INFO] Building remote-plugin-sample 6.7.0-SNAPSHOT

[INFO] --------------------------------[ jar ]---------------------------------

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time:  1.805 s

[INFO] Finished at: 2020-01-25T12:16:54+05:30

[INFO] ------------------------------------------------------------------------

[ERROR] Unknown lifecycle phase "vaidate". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]

org.apache.maven.lifecycle.LifecyclePhaseNotFoundException: Unknown lifecycle phase "vaidate". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy.

    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings (DefaultLifecycleExecutionPlanCalculator.java:248)

    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions (DefaultLifecycleExecutionPlanCalculator.java:217)

    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:126)

    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:144)

    at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan (BuilderCommon.java:97)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:111)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)

    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)

    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)

    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:498)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

[ERROR]

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException

Following is the mvn clean install output:

C:\Users\kumart\Downloads\vsphere-client-sdk-6.7.0.40000-14186396\html-client-sdk\samples\remote-plugin-sample

λ mvn clean install -e

[INFO] Error stacktraces are turned on.

[INFO] Scanning for projects...

[WARNING]

[WARNING] Some problems were encountered while building the effective model for com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT

[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 263, column 18

[WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ line 174, column 18

[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ line 247, column 18

[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-install-plugin is missing. @ line 131, column 18

[WARNING]

[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.

[WARNING]

[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.

[WARNING]

[INFO]

[INFO] --------------< com.vmware.samples:remote-plugin-sample >---------------

[INFO] Building remote-plugin-sample 6.7.0-SNAPSHOT

[INFO] --------------------------------[ jar ]---------------------------------

[WARNING] The POM for com.vmware.vim25:vim25:jar:6.7.0 is missing, no dependency information available

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time:  6.869 s

[INFO] Finished at: 2020-01-25T12:18:59+05:30

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal on project remote-plugin-sample: Could not resolve dependencies for project com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project remote-plugin-sample: Could not resolve dependencies for project com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:269)

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)

    at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)

    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)

    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)

    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:498)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project com.vmware.samples:remote-plugin-sample:jar:6.7.0-SNAPSHOT: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

    at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:209)

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)

    at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)

    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)

    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)

    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:498)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

    at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:357)

    at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:202)

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)

    at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)

    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)

    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)

    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:498)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:424)

    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229)

    at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:340)

    at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:202)

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)

    at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)

    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)

    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)

    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:498)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure to find com.vmware.vim25:vim25:jar:6.7.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

    at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException (DefaultUpdateCheckManager.java:218)

    at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact (DefaultUpdateCheckManager.java:193)

    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads (DefaultArtifactResolver.java:559)

    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads (DefaultArtifactResolver.java:483)

    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:401)

    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229)

    at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:340)

    at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:202)

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243)

    at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147)

    at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)

    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)

    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)

    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)

    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke (Method.java:498)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

[ERROR]

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

I'm using maven 3.6.3

I am trying to automate the installation of esxcli installation in ubuntu , how to automate the license acceptance steps?

I used vsphere.core.inventory.objectViewTemplate/objectCollectionTemplate to created my ListView.

And, I hava interface (DataProviderAdapter) to use for getData().

But now vsphere.core.inventory.objectViewTemplate/objectCollectionTemplate will be deprecate ,

so they will can't be use.

Now, i use the vise.global.views ,and call my html , but i cant use DataProviderAdapter.getData().

so can you tell me , How can I use getDate() By DataProviderAdapter, but we can not use the objectViewTemplate/objectCollectionTemplate.

Please!! and Thanks!!

Hi,

Can you provide Plugin Seed for Remote plugin to support Dev and plugin mode with angular 8 and clarity 2.x as stack?

This will help partners to start/think on migration of plugin to latest architecture.

Thanks,

Kumar

Hi P2V a 2008 R2 server running Citrix 6.5. The P2V went successfully and when its running on the virtual environment i provided it the correct network configuration as below.

1On physical server this OS was running on VLAN 164 and HP blade server.

2. On the virtual environment im using DV switch. Staric ip which was on original box has been assigned to Vm pointing to Vlan 164.

3. i created a DV port and configured it for Vlan 164.

4. On the physical NIC'S on the hosts i could see the IP-Range of the Vlan 164 being presented.

5. I used E1000 as the virtual NIC on the VM and also tried VXnet3 network adapter.

6. This VM connected fine to the network for 2 days and suddently disconnected and wont connect again. Also the Vlan 164 IP range is not presented no longer by the physical Nics on the hosts in the cluster.

7. The physical Box has been shutdown since the P2V took place and never brought up.

8 even when i add vxnet 3 as the additional network  that network adapter fails to get any IP from any dhcp.

9 Vm tools have been installed on the VM successfully and i ahve tried rebooting multiple times but it wont connect .

what are my options here to make it connect to the network.

Hi,

We have a case where we have added host to vCenter and that host has been assigned a UUID based on the physical server bios settings.

Now we have updated our physical server firmware which has few changes to bios settings as well. So for that host/vCenter to pick up the latest bios settings, what needs to be done other than removing the host and adding it back.

IS DISKINTERNALS VMFS SOFTWARE IS LEGIT or CAN BE TRSUTED?

amarinovcontinuum@

This is an ESXi 6.7. This is part of our VSAN 6.7

I have download 6.7u3 sdk and followed various places but could not find proper plugin.xml configuration reference to 

do wizard configuration where my plugin component can come as clarity wizard.

Please help me out 

I want to create a tab on the center pane of vCenter to monitor all ESXi hosts.

As shown below:

The plugin I developed before can only generate a tab under the Monitor tab of the ESXi.

May I ask if it is possible to create a tab to the center pane?

Thanks.

Hi _vladi_

In our vSphere client H5 plugin, we need to add the dynamic port entry into the firewall of VCSA, is there any option to add the port using the VCSA SSO username?

Thanks

Sujeet Kalaskar

We have the custom object list as below, on which we right-click for operation delete. We would like to delete the multiple objects at once.

Is there any way to handle this in vSpeher client 6.7 SDK.  The list does not allow multi-row selection. But if we don same for vSpehere core objects like cluster/host/VM we can do multi-row select

tried the acceptsMultipleTargets = true , but didd not work, Below is the extension point for action:

<extension id="com.xxx.snapshot.actions.deleteSnapshotAction">

      <extendedPoint>vise.actions.sets</extendedPoint>

      <object>

         <actions>

            <com.vmware.actionsfw.ActionSpec>

               <uid>com.xxxx.vcplugin.snapshot.actions.deleteAction</uid>

               <label>#{snapshotdelete.action.label}</label>

               <acceptsMultipleTargets>true</acceptsMultipleTargets>

               <delegate>

            <className>com.vmware.vsphere.client.HtmlPluginModalAction</className>

            <object>

                 <root>

                        <actionUrl>/ui/xxxx/index.html?view=remove-snapshot</actionUrl>

                        <dialogTitle>#{xxxx.deleteSnapshot.title}</dialogTitle>

                        <dialogSize>700,125</dialogSize>

                </root>

            </object>

          </delegate>

            </com.vmware.actionsfw.ActionSpec>

          </actions>

          </actions>

      </object>

</extension>

The local plugin's plugin.xml allowed the addition of separators in context menus with:

<com.vmware.actionsfw.ActionMenuItemSpec>

  <type>separator</type>

</com.vmware.actionsfw.ActionMenuItemSpec>

Does the remote plugin's plugin.json have an equivalent?

Hi All,

Is there any way to add vCSA as remote host in VisualVm for monitoring the java performance due to installing the local HTML5 plugin?

We need to monitor the vSphere-ui when the plugin is not installed and installed.

Thanks,

Vijay

In our current local plugin, we use the vim25.jar library for most integrations. However, we also use sms.jar and pbm.jar available from the VMware vSphere Management SDK for some additional features. In the local plugin case, we are able to create sessions for these libraries using the session cookie available from the ServerInfo object retrieved from the UserSession that is part of the vsphere-client-lib's UserSessionService interface. However, in the remote plugin architecture it does not appear that we have access to the session cookie through similar paths. Additionally, the SmsPortType and PbmPortType classes do not have the cloneSession method available on VimPortType.

What is the correct way to create SmsPortType and PbmPortType objects in the remote plugin architecture which share the user's session the same way the VimPortType object in the sdk sample does?

Hi folks,

The much anticipated vSphere 7.0 release is now GA! With it there is a new 7.0 version of the vSphere Client SDK.

Here are some highlights:

• Plugin Auto-discovery - all new, deleted or changed plugin registrations are immediately detected and trigger deployment/undeployment on the vSphere Client. User is required to only reload the browser to refresh the added/removed extensions.
• RBAC support for managing plugins.
• A bunch of new JS APIs mostly supporting handling user settings and different topologies with remote plugins.
• There are no deprecated or removed APIs.
• Plugin developer mode for quick remote plugin redeployment during development.

For a full list please check the release notes. Check also the new Hands-on-lab and video to get started with remote plugin development:

As usual, please keep the feedback and questions coming! Thanks you!

Cheers,

Vladi

Which VMware SDK should I use to programmatically disable Client Plug-ins?

From vSphere Web Client UI I can do it by going to Administration -> Solutions -> Client Plug-ins, right-click and disable plugin.

Thanks

I found an older post on these forums containing example code for filtering extensions that isn't working for me in 6.7.u2 for my HTML5 plug-in.  The plug-in is never visible even when customProperty returns true.  Could you tell me where the mistake is?

   <extension id="com.violin.violinplugin.datastore.configureView">

      <extendedPoint>vsphere.core.datastore.manageViews</extendedPoint>

      <object>

         <name>Violin Storage</name>

         <contentSpec>

            <url>/ui/violinplugin/resources/datastore-edit.html</url>

         </contentSpec>

      </object>

      <metadata>

          <objectType>Datastore</objectType>

          <propertyConditions>

              <com.vmware.data.query.CompositeConstraint>

                 <nestedConstraints>

                     <com.vmware.data.query.PropertyConstraint>

                       <propertyName>customProperty</propertyName>

                       <comparator>EQUALS</comparator>

                       <comparableValue>

                          <Boolean>true</Boolean>

                       </comparableValue>

                     </com.vmware.data.query.PropertyConstraint>

                 </nestedConstraints>

                 <conjoiner>AND</conjoiner>

              </com.vmware.data.query.CompositeConstraint>

          </propertyConditions>

       </metadata>    

   </extension>  

PropertyProviderAdapter code (with a slightly modified constructor signature) copied off these forums:

public class ViolinPropertyAdapter implements PropertyProviderAdapter {

private Log _logger = LogFactory.getLog(ViolinPropertyAdapter.class);

private static final String CUSTOMPROPERTY = "customProperty";

public ViolinPropertyAdapter(DataService dataService,

     ObjectReferenceService objectReferenceService,

     DataServiceExtensionRegistry extensionRegistry,

     UserSessionService userSessionService) {

     TypeInfo vmTypeInfo = new TypeInfo();

     vmTypeInfo.type = "Datastore";

     vmTypeInfo.properties = new String[]{CUSTOMPROPERTY};

     TypeInfo[] providerTypes = new TypeInfo[]{vmTypeInfo};

     extensionRegistry.registerDataAdapter(this, providerTypes);

}

@Override

public ResultSet getProperties(PropertyRequestSpec propertyRequest) {

     _logger = LogFactory.getLog(ViolinPropertyAdapter.class);

     _logger.info("getProperties()");

     ResultSet result = new ResultSet();

     try {

     List<ResultItem> resultItems = new ArrayList<ResultItem>();

     if(propertyRequest.properties != null && propertyRequest.properties.length > 0) {

     String[] listPropertyNames = propertyRequest.properties[0].propertyNames;

     for(String propertyName : listPropertyNames) {

          for(Object dsRef : propertyRequest.objects) {

          ResultItem resultItem = getDsProperties(dsRef, propertyName);

          if(resultItem != null) {

          resultItems.add(resultItem);

     }

     }

     }

     } else

     result.items = resultItems.toArray(new ResultItem[]{});

     } catch(Exception e) {

     // Passing the exception in the result allows to display an error

     // notification

     // in the client UI.

     result.error = e;

     }

     return result;

}

private ResultItem getDsProperties(Object dsRef, String propertyName) throws InvalidPropertyFaultMsg, RuntimeFaultFaultMsg {

     ResultItem ri = new ResultItem();

     ri.resourceObject = dsRef;

     PropertyValue pvCustomProperty = new PropertyValue();

     pvCustomProperty.resourceObject = dsRef;

     pvCustomProperty.propertyName = CUSTOMPROPERTY;

     boolean val = new Random().nextBoolean();

     _logger.info(CUSTOMPROPERTY + "=" + val);

     pvCustomProperty.value = val;// here taken the random boolean value which will load in

     // plugin.xml. On true return you can filter the extension

     // point using property

     ri.properties = new PropertyValue[]{pvCustomProperty};

     return ri;

}

}

And finally, the entries in my log file, that shows the PropertyProviderAdapter  being called:

[2020-04-08 23:02:58] [INFO] com.violin.violinplugin.adapters.ViolinPropertyAdapter:44 - getProperties()

[2020-04-08 23:02:58] [INFO] com.violin.violinplugin.adapters.ViolinPropertyAdapter:76 - customProperty=false

[2020-04-08 23:03:14] [INFO] com.violin.violinplugin.adapters.ViolinPropertyAdapter:44 - getProperties()

[2020-04-08 23:03:14] [INFO] com.violin.violinplugin.adapters.ViolinPropertyAdapter:76 - customProperty=false

[2020-04-08 23:03:15] [INFO] com.violin.violinplugin.adapters.ViolinPropertyAdapter:44 - getProperties()

[2020-04-08 23:03:15] [INFO] com.violin.violinplugin.adapters.ViolinPropertyAdapter:76 - customProperty=true

[2020-04-08 23:03:17] [INFO] com.violin.violinplugin.adapters.ViolinPropertyAdapter:44 - getProperties()

[2020-04-08 23:03:17] [INFO] com.violin.violinplugin.adapters.ViolinPropertyAdapter:76 - customProperty=true

If you could give me a working code example of filtering based of a datastore property for 6.7, or tell me what needs to be fixed in the simple example I've included, that'd really help me out.  Thanks!

I want to display VM console created by vsphere in browser.So I use the html5 console sdk.

Here is the sdk https://code.vmware.com/samples/1117/showing-web-console-of-a-vm-via-vsphere-html-console-sdk#.

Here is the sdk document https://code.vmware.com/docs/9197/html-console-sdk-programming-guide/GUID-632AC4ED-3292-4901-8CFC-1FAC4C37DA37.html

I use the second method. The webmksTicket method.  But it show some error.

Here is my code:

<!DOCTYPE html PUBLIC"-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta http-equiv="content-type" content="text/html; charset=utf-8" />
  <title>Console</title>
</head>
<body>
<h1>This is a sample of showing Web Console of a VM in vCenter 6.0.</h1>
<link rel="stylesheet" type="text/css" href="./css/wmks-all.css" />
<script type="text/javascript" src="./jquery-3.5.0.min.js"></script>
<script type="text/javascript" src="./jquery-ui.min.js"></script>
<script type="text/javascript" src="./wmks.min.js"></script>
<div id="wmksContainer" style="position:absolute;width:100%;height:100%"></div>
<script>
   var wmks = WMKS.createWMKS("wmksContainer",{})

  .register(WMKS.CONST.Events.CONNECTION_STATE_CHANGE, function(event,data){

   if(data.state == WMKS.CONST.ConnectionState.CONNECTED){

   console.log("connection state change : connected");}

  });
   wmks.connect("wss://ESXi_IP:443/ticket/d9c3b2f517ba1685");
</script>
</body>
</html>

Here is my error in browser console:

wmks.min.js:1 WebSocket connection to 'wss://ESXi_IP:443/ticket/d9c3b2f517ba1685' failed: Error during WebSocket handshake: Unexpected response code: 503

telnet ESXi_ip 443 is fine

This webmksTicket number is obtained according to the tutorial in this sdk document.It should be correct.

I'm using vsphere 6.7.    I open the html by nginx1.16.1     I use the html5 console sdk 2.1.0   

Can anyone tell me what should I do. Or is there any other way for me to display the virtual machine console in the browser.

Hi guys,

I have a concern regarding on SDK for our VMware esxi hypervisor 6.0.0, I need to resolve this issue to make my telegraf/influxdb to work for my grafana

our other VMware can be visited take a look on the picture below..

but one of our VMware can't be visited, take a look on the picture below...

I think this is why my telegraf and InfluxDB can't read the metrics graph for my GRAFANA

any solution for this? i don't have any knowledge to explore it yet and our previous IT didn't turnover any of this, Thank you...

should I install a SDK?

should I go to vmware cli?

please Help thank you...

Hi,

We had upgraded our plugin service layer spring version as per the upgrade guide(attached) from VMware to support with 6.5U2 and above.

Our plugin is not coming up on vCenter 6.7U1 but it is working fine in 6.5U2, 6.5U2, 6.7U2, 6.7U3 and 7.0GA as well.

Below is the conflict snippet from virgo server log:

[2020-06-12T14:11:46.557Z] [INFO ] fs-watcher                    o.e.virgo.kernel.userregion.internal.quasi.DependencyCalculator   Calculating missing dependencies of bundle(s) 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui_9.7.0' [2020-06-12T14:11:46.649Z] [INFO ] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         ME0003I Dump '/usr/lib/vmware-vsphere-ui/server/serviceability/dump/2020-06-12-14-11-646' generated [2020-06-12T14:11:46.665Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0002E Installation of par 'com.acme.prodh5' version '9.7.0.23531' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' at version '9.7.0': Cannot resolve: com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui    Resolver report:        An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui_9.7.0>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}
        An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-synthetic.context_9.7.0.23531>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0"> constrained to bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service> constrained bundle version range "[9.7.0,9.7.0]"            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}
        A bundle could not be resolved because the required generic capability could not be resolved. Resolver error data <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service_9.7.0>             constraint: <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:46)at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:73)at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:359)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:185)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:140)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:253)at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225)at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79)at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380)at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289)at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49)at java.lang.Thread.run(Thread.java:748)
[2020-06-12T14:11:46.666Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' version '9.7.0' [2020-06-12T14:11:46.666Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' version '9.7.0'. [2020-06-12T14:11:46.667Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for bundle 'com.acme.prodh5-9.7.0.23531-com.vmware.wsvim25' version '6.7.0' [2020-06-12T14:11:46.667Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for bundle 'com.acme.prodh5-9.7.0.23531-com.vmware.wsvim25' version '6.7.0'. [2020-06-12T14:11:46.668Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for bundle 'com.acme.prodh5-9.7.0.23531-com.google.gson' version '2.3.1' [2020-06-12T14:11:46.668Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for bundle 'com.acme.prodh5-9.7.0.23531-com.google.gson' version '2.3.1'. [2020-06-12T14:11:46.668Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service' version '9.7.0' [2020-06-12T14:11:46.669Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service' version '9.7.0'. [2020-06-12T14:11:46.669Z] [INFO ] fs-watcher                    o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing install failed event for par 'com.acme.prodh5' version '9.7.0.23531' [2020-06-12T14:11:46.670Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for par 'com.acme.prodh5' version '9.7.0.23531'. [2020-06-12T14:11:46.672Z] [ERROR] plugin-deploy11               com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/com.acme.prodh5-9.7.0.23531 java.lang.Exception: Bundle: <com.acme.prodh5,9.7.0.23531> failure: Install Failedat com.vmware.vise.extensionfw.impl.BundleLifeCycleListenerImpl.collectDeployFailure(BundleLifeCycleListenerImpl.java:156)at com.vmware.vise.extensionfw.impl.BundleLifeCycleListenerImpl.onInstallFailed(BundleLifeCycleListenerImpl.java:76)at org.eclipse.virgo.kernel.install.artifact.internal.StandardArtifactStateMonitor.onInstallFailed(StandardArtifactStateMonitor.java:132)at org.eclipse.virgo.kernel.install.artifact.internal.AbstractInstallArtifact.failInstall(AbstractInstallArtifact.java:120)at org.eclipse.virgo.kernel.deployer.core.internal.Plumber$3.operate(Plumber.java:116)at org.eclipse.virgo.kernel.install.pipeline.stage.visit.internal.VisitationStage.doProcessNode(VisitationStage.java:51)at org.eclipse.virgo.kernel.install.pipeline.stage.visit.internal.VisitationStage.doProcessGraph(VisitationStage.java:65)at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.compensate(CompensatingPipeline.java:93)at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:78)at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:359)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:185)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:140)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:253)at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225)at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79)at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380)at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289)at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49)at java.lang.Thread.run(Thread.java:748)
[2020-06-12T14:11:46.672Z] [INFO ] plugin-deploy11               com.vmware.vise.extensionfw.impl.HotDeployBundleDeployer          Deleting bundle file: /usr/lib/vmware-vsphere-ui/server/pickup/com.acme.prodh5-9.7.0.23531.par [2020-06-12T14:11:46.675Z] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0500E Unable to install application from URI 'file:/usr/lib/vmware-vsphere-ui/server/pickup/com.acme.prodh5-9.7.0.23531.par'. Cannot satisfy constraints for bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' version '9.7.0'. Cannot resolve: com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui    Resolver report:        An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui_9.7.0>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}
        An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-synthetic.context_9.7.0.23531>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0"> constrained to bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service> constrained bundle version range "[9.7.0,9.7.0]"            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}
        A bundle could not be resolved because the required generic capability could not be resolved. Resolver error data <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service_9.7.0>             constraint: <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui' at version '9.7.0': Cannot resolve: com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui    Resolver report:        An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-ui_9.7.0>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="1.0.0">            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}
        An Import-Package could not be resolved. Resolver error data <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-synthetic.context_9.7.0.23531>             constraint: <Import-Package: com.acme.myhtmlplugin.vcenter.service; version="0.0.0"> constrained to bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service> constrained bundle version range "[9.7.0,9.7.0]"            with attributes {module_scope=com.acme.prodh5-9.7.0.23531}
        A bundle could not be resolved because the required generic capability could not be resolved. Resolver error data <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">. Caused by missing constraint in bundle <com.acme.prodh5-9.7.0.23531-com.acme.myhtmlplugin.myhtmlplugin-service_9.7.0>             constraint: <Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))">
at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:46)at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:73)at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:359)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:185)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:140)at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:253)at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225)at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79)at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380)at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289)at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49)at java.lang.Thread.run(Thread.java:748)

Service layer manifest file:

Manifest-Version: 1.0

Bundle-Vendor: acme

Bundle-Version: 9.7.0

Tool: Bundlor 1.1.0.RELEASE

Bundle-Name: myhtmlplugin-service

Bundle-ManifestVersion: 2

Bundle-SymbolicName: com.acme.myhtmlplugin.myhtmlplugin-service

Export-Package: com.acme.myhtmlplugin.mvc;version="1.0.0",

com.acme.myhtmlplugin.util;version="1.0.0",

com.acme.myhtmlplugin.dashboard.service;version="1.0.0",

com.acme.myhtmlplugin.storagesystem.service;version="1.0.0",

com.acme.myhtmlplugin.datastore.service;version="1.0.0",

com.acme.myhtmlplugin.storage.service;version="1.0.0",

com.acme.myhtmlplugin.privileges.service;version="1.0.0",

com.acme.myhtmlplugin.reports.service;version="1.0.0",

com.acme.myhtmlplugin.home.service;version="1.0.0",

com.acme.myhtmlplugin.appliance.service;version="1.0.0",

com.acme.myhtmlplugin.vcenter.service;version="1.0.0",

com.acme.myhtmlplugin.vvolreports.service;version="1.0.0",

com.acme.myhtmlplugin.datastore.service;version="1.0.0",

com.acme.myhtmlplugin.privileges.service;version="1.0.0",

com.acme.myhtmlplugin.managecapability.service;version="1.0.0",

com.acme.myhtmlplugin.vsphereportlet.service;version="1.0.0",

com.acme.myhtmlplugin.thresholds.service;version="1.0.0",

com.acme.myhtmlplugin.nfsvaai.service;version="1.0.0",

com.acme.myhtmlplugin.inventory.service;version="1.0.0",

com.acme.myhtmlplugin.vsphereentity.service;version="1.0.0",

com.acme.myhtmlplugin.hosts.service;version="1.0.0",

com.acme.myhtmlplugin.storagemapping.service;version="1.0.0",

com.acme.myhtmlplugin.esxihost.service;version="1.0.0",

com.acme.myhtmlplugin.credentials.service;version="1.0.0",

com.acme.myhtmlplugin.storagecapabilityprofile.service;version="1.0.0",

com.acme.myhtmlplugin.vvoldashboard.service;version="1.0.0"

Import-Package: org.apache.commons.logging;version="1.1.1",

com.vmware.vise.data;version="0",

com.vmware.vise.data.query;version="0",

com.vmware.vise.data.uri;version="0",

com.vmware.vise.usersession;version="0",

com.vmware.vise.security;version="0",

com.vmware.vise.vim.data;version="0",

com.vmware.vim25;version="6.5.0",

com.google.gson;version="2.3.1",

javax.servlet.http;version="3.0",

javax.net.ssl;version="0",

org.springframework.beans.factory.annotation;version="0",

org.springframework.http;version="0",

org.springframework.stereotype;version="0",

org.springframework.web.bind.annotation;version="0",

org.springframework.web.client;version="0",

org.springframework.util;version="0",

org.springframework.web.util;version="0"

UI layer Manifest file:

Manifest-Version: 1.0

Bundle-ManifestVersion: 2

Bundle-Name: myhtmlplugin-ui

Bundle-SymbolicName: com.acme.myhtmlplugin.myhtmlplugin-ui

Bundle-Version: 9.7.0

Bundle-Vendor: acme

Web-ContextPath: vsphere-client/myhtmlplugin

Import-Package: com.acme.myhtmlplugin.mvc;version="1.0.0",

com.acme.myhtmlplugin.storage.service;version="1.0.0",

com.acme.myhtmlplugin.storagesystem.service;version="1.0.0",

com.acme.myhtmlplugin.util;version="1.0.0",

com.acme.myhtmlplugin.dashboard.service;version="1.0.0",

com.acme.myhtmlplugin.reports.service;version="1.0.0",

com.acme.myhtmlplugin.storagecapabilityprofile.service;version="1.0.0",

com.acme.myhtmlplugin.home.service;version="1.0.0",

com.acme.myhtmlplugin.appliance.service;version="1.0.0",

com.acme.myhtmlplugin.vcenter.service;version="1.0.0",

com.acme.myhtmlplugin.datastore.service;version="1.0.0",

com.acme.myhtmlplugin.vvolreports.service;version="1.0.0",

com.acme.myhtmlplugin.privileges.service;version="1.0.0",

com.acme.myhtmlplugin.vsphereportlet.service;version="1.0.0",

com.acme.myhtmlplugin.managecapability.service;version="1.0.0",

com.acme.myhtmlplugin.nfsvaai.service;version="1.0.0",

com.acme.myhtmlplugin.inventory.service;version="1.0.0",

com.acme.myhtmlplugin.vsphereentity.service;version="1.0.0",

com.acme.myhtmlplugin.esxihost.service;version="1.0.0",

com.acme.myhtmlplugin.thresholds.service;version="1.0.0",

com.acme.myhtmlplugin.hosts.service;version="1.0.0",

com.acme.myhtmlplugin.storagemapping.service;version="1.0.0",

com.acme.myhtmlplugin.credentials.service;version="1.0.0",

com.acme.myhtmlplugin.vvoldashboard.service;version="1.0.0",

com.vmware.vise.data.query;version="0",

com.vmware.vise.security;version="0",

org.eclipse.virgo.web.dm;version="3.6.0",

org.springframework.web.servlet;version="3.1.4",

org.springframework.web.servlet.view;version="3.1.4",

org.springframework.web.servlet.view.json;version="3.1.4",

org.springframework.web.servlet.config;version="3.1.4"

Please suggest what is wrong?

Is there a know issue with in VC 6.7U1?

Thanks,

Kumar

Hi,

We have developed a vCenter Html plugin two years back with technologies in UI like, Angular, Clarity design system .... There was also lot new developments on the backend.

Now we are in the process of developing remote plugin.

First off i am trying to research / understand what is the difference between the previous one and the new remote plugin?. Any pointers in this regard... (I am reading the vsphere-client-sdk-673-remote-programming-guide.pdf for now)

Also while going over the documentation of vsphere-client-sdk-673-remote-programming-guide.pdf found few new things, like below.

• In the documentation it says to use the new plugin user JavaScript interfaces with htmlClientSdk.js, called, model, app, event... But in our existing plugin-ui we were using WEB_PLATFORM referencing from window.parent.
• Found the plugin manifest file type is changed to plugin.json. Previously it was plugin.xml file with its own definitions of plugin, resources, extension.. Now I am not sure how much of this is supported with new format of manifest file type plugin.json.

Now should we update our plugin code as per new guide. I am seeing in the guide that accessing window.parent is not recommanded... PFA screenshot.

Please share few inputs, thanks.

Our team is using SDK v6.7 update 3, and the following code:

    public void contextInitialized(ServletContextEvent sce) {
         final ServletContext servletContext = sce.getServletContext();
         final ServerContainer globalPassthru = (ServerContainer)servletContext.getAttribute("javax.websocket.server.ServerContainer");
         .
         .
     }     

Invariably throws a ClassCastException:

    com.vmware.o6jia.context.web.websocket.ServerContainerWrapper cannot be cast to javax.websocket.server.ServerContainer 

However, if the plugin is deployed in global scope, the code above works flawlessly. We've already attempted setting/resetting context classloader as described here:

    Thread.currentThread().setContextClassLoader(getClass().getClassLoader())

Does removing <code>scope="global"</code> from pluginPackage involve additional configuration?

Hi,

Is there someone can help me where can i find the older logs on search backups function.

Thanks.

Hello,

I develop a vCenter plugin which imports 3rd party jar files. I've run into a vCenter version incompatibility. As of around either late 6.7u2 or 6.7u3, my plugin no longer registers successfully. I am unsure of what I need to do or change in order to get it working on these newer vCenter versions, and why it would only throw these errors on the newer versions. An example of the error is listed below.

vsphere_client_virgo.log:[2020-05-16T00:19:58.509Z] [ERROR] vc-extensionmanager-pool-235  com.vmware.vise.extensionfw.plugins.impl.PluginStatusServiceImpl DEPLOYMENT_FAILED: Error deploying plugin package com.hpe.vnsui:1.4.9.0. Reason: Deployment error. java.io.IOException: The bundle at /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/com.hpe.vnsui-1.4.9.0/plugins/httpcore-4.4.9.jar should have Bundle-SymbolicName and Bundle-Version headers in its MANIFEST.MF

Any help would be appreciated. Thank you.

Hi folks,

The RC bits of the next 7.0 update release can be downloaded from the Beta community.

It contains quite some new features and improvements to the SDK and plugins.

If you are not a beta partner please consider becoming one and contact vSphere_Beta_Team@VMware.com

Please report through the Beta community or DCPN any feedback you might have. Thanks!

Cheers,

Vladi

Hi,

I used vsphere 6.7 sdk , like this:

  navigateToSummaryView(objectId): void {

    const selectedTarget = this.selectedTargets;

    this.storagepluginService.htmlClientSdk.app.navigateTo({

      targetViewId: 'com.xxxxxxx.summary',

      objectId: objectId,

      customData: { objectId, selectedTarget }

    });

  }

and i want to get "objectId" from "targetViewId",

so i use 2 htmlClientSdk :

1. htmlClientSdk.app.getNavigationData()

2. htmlClientSdk.htmlClientSdk.app.getContextObjects()[0]

they can worked.

But 1. (getNavigationData) have probleme , they can't ued by browser's Refresh/Next Page/Back Page

they will make getNavigationData() to be undefined

so I used 2. getContextObjects()[0].

But In vSphere 7.0, [2. getContextObjects()[0]] can't work

So I need to know, have any way to fix this?

Hi _vladi_ and laurentsd,

Is there any way to get an indication that plugin is going to be unregistered before, so that we can do some clean up?

Suppose, we have a logs created for the plugin which we have registered.

During unregister we want to clean the plugin's log directory.

Note: Register/Unregister is done using the extension-registration script provided in SDK.

Can you please help?

Thanks

Sujeet Kalaskar

Hi VMWare Community,

In order to develop and debug our custom plugin (as a team), we need to deploy and run it on our local machines. Here are some details:

What do we do:

Local environment setup:

• We download the vSphere Client SDK 7.0.0.10100 or 6.7.20000 to local machine (depending on vcenter version)
  • We unpack the content locally and set required environment variables: VMWARE_CFG_DIR,VSPHERE_SDK_HOME
  • We have correct JAVA_HOMEand MAVEN_HOME defined
• We run the server-registration.bat script from vcenter SDK to generate three required files (store.jks, webclient.properties and ds.properties) and we store them under correct locations in ProgramFIles\VMWare\vCenterServer\cfg\ 
  • server-registration.bat -vcip [our-vcenter-IP] -u [user] -pw [thePassword]
• At the very end, we run the startup.bat script from \html-client-sdk\vsphere-ui\server\bin in order to locally run the environment with debug option
  • startup.bat -debug 6969 
• After a couple of minutes, if everything works ok, setup script is completed and we can access the local environment by entering the https://localhost:9443/ui , login and see the content of the vcenter locally.

What does not work:

In spite of the fact that all team members follow same steps, some group of them are not able to start the plugin correctly. Here you can see the symptoms:

1) Installation process hangs on the following phase and doesn't process any further

2) When trying to login we can see an error message indicating a authentication problem:

3) In virgo logs we can observe:

[2020-08-04T07:30:24.368+02:00] [ERROR] cm-catalog-manager-pool-12    com.vmware.vim.sso.client.impl.SoapBindingImpl                    SOAP fault com.sun.xml.internal.ws.fault.Ser
verSOAPFaultException: Client received SOAP Fault from server: Signature is invalid. Please see the server log to find more detail regarding exact cause of the failure.         at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)         at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:116)         at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:259)

Main question:

According to us, there is something wrong with certificates on local machines (only few people are affected in the team). Not sure what exactly. Should we think about any other certificates than these in Java keystore (according to JAVA_HOME) or store.jks (generated from vcenter) ? Do you have any ideas what can be the cause or where should we look for it?

What we've already tried (with no effect):

• Going through the same procedure (using the same vcenters) by different team members
• Generating the store.jks by people who do not have problems any use it by other user
• Copying the jre keystore (from JAVA_HOME) from people who do not have problems
• Members facing this problem tried to use different vcenters as well
• Examining the local firewall logs did not revealed any blocked traffic
• We also try to perform the entire setup procedure from scratch, many times removing the following files/dirs before:
  • C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cmCatalog
  • C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cm-service-packages
  • C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages
  • C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\compatability-matrix.xml.

Please let me know if I should add any other information. All help is appreciated.

Regards,

Radoslaw

Hi Team,

I'm trying to test Singleton Plug-in topology as mentioned in Remote plugin SDK documentation(vsphere-client-sdk-7.0.0.10100-15863815).

In order to test that, I had registered same instance of plugin with multiple vCenter servers(of 7.0 version in Enhanced Linked Mode) and able to see the plugin by connecting to both vCenters.

But the chassis list actions are always listing VC1 related host list only which is used for manifest server startup command as shown below:

java -jar target/remote-plugin-sample-6.7.0-SNAPSHOT.jar --vcenter.guid=5xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx --vcenter.thumbprint=1xxxxxxxxxxxxxxxxxxxxxxxxxx --vcenter.fqdn=vc1.com --vcenter.port=443

Below are the queries:

1. Is it possible to achieve the singleton plugin instance working using the given sdk sample and tools? If so what is the command options we should use to support multiple vCenters?

2. What are the file/function changes we need to make in service/ui code to support this routing?

Thanks

Shravan

Message was edited by: shravansofts

Hi Team,

We are observing rending issues for our local plugin with vCenter client 7.0.0.10100 and Google chrome v70.0.3538.77. In order to reproduced i had used vCenter client SDK 7.0 remote plugin  sample as shown in the attached gif. But plugins(local/remote) rendering works fine in later chrome versions say v80, v85 etc and on Mozilla firefox.

As per VMWare official documentation it supposed to work from chrome v50 and above.

Please clarify whether it is bug or any change in recommended minimum chrome browser.

Thanks,

Kumar

My development cloud recently moved from public to a private lan , after that I am failing to register my local vSphere Client with a new vCenter. I keep getting the Auth fail error.Pasting the error below

"VMWARE_CFG_DIR is chosen to be: C:/ProgramData/VMware/vCenterServer/cfg/

Has connection problem with vCenter server IP: 192.168.36.202. Please check vCenter server and authentication.

 Auth fail"

Rather than changing the ip address, username and password of the new vCenter in the command "server-registration.bat -vcip <new ip>  -u <new username>  -pw <new password> -p 22 -v, is there anything else I need to change. I am able to connect through ssh and browser.

Hi plugin developers,

vSphere 7.0U1 is out. The new vSphere Client SDK contains cool new stuff for plugins, most notably:

- Dynamic remote plugin extensions (ability to show/hide plugin items).

- Plugin multi-manifest support (enables taking advantage of new APIs while preserving compatibility with older vSphere Client releases).

- Actions on multiple targets (e.g. on a selection of multiple VMs).

Meanwhile the vSphere Client has made a huge step forward with accessibility & icons. We recommend plugins to follow suit and make plugin views more accessible.

If you have any suggestions or ideas on how to improve the vSphere Client or the plugin support you can now use the vSphere Ideas section of the Client's Feedback menu (top-right).

SDK bits & docs: SDK home page, Release Notes

Cheers,

Vladi

Hi all,

I want to develop my custom vCenter plugin, so I deploy vSphere Client SDK in my development machine, but in the end, I failed to access https://localhost:9443/ui, it shows that "[400] An error occurred while sending an authentication request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - null."

Help highly appreciated

What I do:

1. my development machine is Windows 10, its environment is:

         --java: 1.8.0_60

         --ant: 1.9.15

    2. I have a VCSA6.7(VMware vCenter Server Appliance 6.7.0), and I can access it normally

     3. Download vSphere Client SDK 6.7.0 from https://code.vmware.com/web/sdk/6.7/client

     4. Extract the content of the SDK in a directory, then set the VSPHERE_SDK_HOME and VMWARE_CFG_DIR environment variables:

   5. Register My Local vSphere Client with the vCenter Server Instance

       -- Run the dev-setup.sh on my VCSA

               root@vcsa158 [ ~ ]# sh dev-setup.sh

               Generating store.jks file...

               Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M

               Importing keystore store.p12 to store.jks...

               Entry for alias vsphere-webclient successfully imported.

               Import command completed:  1 entries successfully imported, 0 entries failed or cancelled

               Warning:

               The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore store.jks                -                      destkeystore store.jks -deststoretype pkcs12".

               Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M

               Certificate was added to keystore

               Warning:

               The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore store.jks                     destkeystore store.jks -deststoretype pkcs12".

               Generating webclient.properties file...

               Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M

               Creating ds.properties file...

               Done.

       --Copy the three generated files on my dev machine

          webclient.properties  --    C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client

          ds.properties  --    C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\config

          store.jks    --    C:\ProgramData\VMware\vCenterServer\cfg

   6. Run the startup script to start the local vSphere Client

7. Failed to access https://localhost:9443/ui

Hi VMWare Community,

I need to create a reporting system from vSphere with data about all clusters in Power BI.

How data can be transfered?

Please help ASAP.