I have a few problems concerning the presentation in the custom web view I created.
I made some screenshots so you understand what I mean exactly.
The first screenshot shows the issue with the object IDs. The second one shows the missing name for the VMs and the third one shows my current properties for the presentation of my VMs.
yep, the # is a typo.
The SdkConnection has to come from the vCO-Inventory.
So in my case I had an input parameter named SdkConnection (you can name it at will) with type VC:SdkConnection for the scripting element.
That's because vCO is designed to deal with more than one vCenter-Server, so there is no global authorisationManager.
Cheers,
Joerg
Hi,
For -1- "Local Datastore 10" does not seem to be and id. Ids are in the datastore-xx form.
Are you sure you do not have this datastore, somewhere ?
For -2-
Root folder only works for treeview
If you want to pick up a VM amongst a list of VM belonging to a folder you can use the predefined list properties and assign it an action that get the vm for this folder Or you can set an attribute of type array of VM and assign it with a fixed list of VMs).
Christophe.
For -3- You can add description for steps and groups 9not individual fields (these support only labels)
Hi, thanks for your help.
regards
-2-
You must be doing differently than I am doing since for me I can get the root element working in treeview mode and the list of predefined VMs.
Are your properties looking like this :
(defaultVms is an array of VMs atribute I have set with 2 VMs)
I have attached the small test workflows I use.
Do you experience same behavior in the client ?
I still wonder why it does not display the object name.
I can't import your workflow because we don't have the same vCO version (picuture 47).
I now set the "Select value as" property to tree view. As you can see there are a lot of properties missing (picture 48), but in vCO client everything works fine (picuture 49).
Try to import this attached package instead of the individual workflows. You may not be able to import wf because they are signed with my certificate that you have never imported.
I really wonder what the webview pb is. have you tried with a different browser ?
Do you have similar issues with the workflows in the library ?
That's strange. Seems to be a global problem. I now imported your workflow and it doesn't work too. I also tried another browser, no difference.
I also tired with copied workflow from the library, I just edited the presentation and added the "Predefined list of elements" property. Same behaviour.
Check if you have errors in app-server/server/vmo/log/server.log when starting a workflow.
I found the following errors and warnings. All of them appear several times when I open the web view. Below the error messages are a lot of lines beginning with "at", do you need them too? The not autenticated warnings are very strange I think. Why does the login work and I'm still not authenticated?
2011-03-11 08:01:06.500+0100 ERROR [VimVirtualMachine] getProperty() [lab.intra\internal@https://localhost:443/sdk/Main#1728cbe6, VirtualMachine<vm-68>] --> Property 'summary' does not exist
com.vmware.vmo.plugin.vi4.model.NoSuchPropertyException
2011-03-11 08:01:07.396+0100 ERROR [VimDatastore] getProperty() [lab.intra\internal@https://localhost:443/sdk/Main#1728cbe6, Datastore<datastore-10>] --> Property 'summary' does not exist
com.vmware.vmo.plugin.vi4.model.NoSuchPropertyException
2011-03-11 08:01:07.461+0100 ERROR [VimSession] getOrCreateVimObject() --> Unable to get Vim class for 'Folder'
2011-03-11 08:01:07.299+0100 WARN [VimSession] invokeWebServiceOperation() [lab.intra\internal@https://localhost:443/sdk/Main#1728cbe6].createFilter --> NotAuthenticated : Die Sitzung wurde nicht authentifiziert., privilege id 'System.View'
2011-03-11 08:01:07.299+0100 WARN [FiltersManager] createPropertyFilter() --> Unable to create the filter
AxisFault
faultCode: ServerFaultCode
faultSubcode:
faultString: Die Sitzung wurde nicht authentifiziert.
faultActor:
faultNode:
faultDetail:
{urn:vim25}NotAuthenticatedFault:<object>datastore-10</object><privilegeId>System.View</privilegeId>
Hi,
german logfile 🙂 Plese check the rights of the user and have a look here: http://mighty-virtualization.blogspot.com/2011/03/vco-internal-methods-and-authorizations.html
I often give the user admin rights and check then if there is an error.
best regards
Christian
Jepp, german! 🙂
I just tried to run the workflow as a domain administrators who's also vCO Administrator and vCenter Server Administrator and the behaviour is still the same. Now I don't know which other rights could be missing. Any ideas?
Hmm. If I compare with the errors in my logfile, the format lab.intra\internal@https://localhost:443/sdk/Main#1728cbe6 looks not like mine: user@https://vCenterServer/sdk/xxxx
In my case the usage of the username without domain was essential. Could you please check that?
best regards
Christian
I tried a few things not, but I wasn't successful. The hint concerning the diffrent looking links, led me to an idea. I tried to make a few changes in "VMware vCenter Orchestrator Configuration -> vCenter Server 4.1 -> hosts". I tried the following:
Sadly nothing worked. The error messages are still the same.
2011-03-11 11:46:53.512+0100 WARN [VimSession] invokeWebServiceOperation() [internal@https://lab-srv002:443/sdk/Main#5df8ab0d].createFilter --> NotAuthenticated : Die Sitzung wurde nicht authentifiziert., privilege id 'System.View'
2011-03-11 11:46:53.513+0100 WARN [FiltersManager] createPropertyFilter() --> Unable to create the filter
AxisFault
faultCode: ServerFaultCode
faultSubcode:
faultString: Die Sitzung wurde nicht authentifiziert.
faultActor:
faultNode:
faultDetail:
{urn:vim25}NotAuthenticatedFault:<object type="VirtualMachine">vm-68</object><privilegeId>System.View</privilegeId>
2011-03-11 11:46:53.615+0100 ERROR [VimVirtualMachine] getProperty() [internal@https://lab-srv002:443/sdk/Main#5df8ab0d, VirtualMachine<vm-68>] --> Property 'summary' does not exist
com.vmware.vmo.plugin.vi4.model.NoSuchPropertyException
The following error message is new I think. At least I haven't seen it before.
2011-03-11 11:47:45.000+0100 DEBUG [WebviewExceptionPage] Webview Exception - message : Error: An error occured processing annotation @org.apache.tapestry.annotations.Parameter(cache=true, name=type, required=true, defaultValue=, aliases=) of public abstract java.lang.String ch.dunes.vso.web.webform.components.editors.ChooserSelectPart.getType(): Parameter type has already been declared (at Annotation @org.apache.tapestry.annotations.Parameter(cache=true, name=type, required=true, defaultValue=, aliases=) of public abstract java.lang.String ch.dunes.vso.web.webform.components.editors.ChooserSelectPart.getType()).
2011-03-11 11:47:45.000+0100 DEBUG [WebviewExceptionPage] Username visitor : username@lab.intra
2011-03-11 11:47:45.000+0100 DEBUG [WebviewExceptionPage] StackTrace :
I attached a picture of my current configuration of the vCenter Server Configuration in vCO Configuration. Can you see any mistakes?
I don't think it's a rights problem because I can see all the properties when I click on the virtual machine (picture 01).
Is there nobody with similar problems? It doesn't even work with actions. I just tried to set the possible options for a parameter using an action and now there aren't any values to choose anymore (see pictures). Except of the 'NotAuthenticated'-errors I found these in the log file.
2011-03-16 10:56:59.895+0100 ERROR [VimSession] getOrCreateVimObject() --> Unable to get Vim class for 'Folder'
2011-03-16 10:56:59.895+0100 ERROR [VimSession] fetchVimReferencesForType('VirtualMachine') [internal@https://lab-srv002:443/sdk/Main#c1a890f] --> Unknown exception
java.lang.NullPointerException
at com.vmware.vmo.plugin.vi4.VimSession.fetchVimReferencesForType(VimSession.java:1059)
at com.vmware.vmo.plugin.vi4.VimSession.fetchVimObjectsForType(VimSession.java:1110)
at com.vmware.vmo.plugin.vi4.VimPluginFactory$FindAllThread.run(VimPluginFactory.java:294)
You seem to have a serious problem having your vCO to communicate properly with your vCenter.
To segregate the issue I would recommend:
What build of vCenter are you using ?
I'm using build 258902 of vCenter Server. Do you really think I have some communication problems? I didn't install vCO separately, I just activated it on vCenter Server. Shoudn't these versions fit to each other? Apart from that, why do I have these problems only in web view? Shouldn't I have these problems in vCO Client too if there were some communication problems?
The version is not the problem. I have the same version here. Just wanted to make sure you did not have a special version.
The log errors you have provided are from the vCO server communicating with the vCenter server. My first thought on this was permissions but sometimes it is good to restart with the basics to understand where the problem is coming from.