Has anyone had any luck connecting to SharePoint with the SOAP plugin?
I can't seem to get the authentication to work, no matter the type of authentication i select.
Error accessing 'http://sharepoint/sites/test/_vti_bin/lists.asmx?WSDL': HTTP/1.1 401 Unauthorized
Hi,
yes, I'm uning the SOAP Plug-in to fill data into sharepoint lists. It's working very stable.
I'm using also the lists.asmx interface. For authentication I'm using "basic" authentication. Username is provided with the netbios domain name: domain\username
Writing into Sharepoint is possible with an Microsoft XML language called CAML:
http://msdn.microsoft.com/en-us/library/lists.lists_methods%28v=office.12%29.aspx
There is also a good CAML builder tool which helps to understand the way CAML is build up. Escpecially Queries in the GetListItems operation.
Greetings Chris
Edit:
If forgott the link for the CAML builder tool: http://www.u2u.be/res/tools/camlquerybuilder.aspx
Thanks for the answer, shoud have replied sooner.
Unfortunately I'm not able to use Basic authentication, only Kerberos and the SOAP plugin does not support Kerberos right now. :smileyplain:
Hi Magnus,
Powershell might be a workaround:
http://technet.microsoft.com/en-us/library/fp161362(v=office.15).aspx
If you really want to dig deep:
The Powershell Plugin for vCO supports Kerberos.
... and is available open source: http://communities.vmware.com/docs/DOC-20354
So feel free to adopt the Kerberos part to create your own shareoint-plugin for vCO :smileysilly:.
Cheers,
Joerg
Were you able to create an External Content Type or create a Web Services data source through SharePoint designer?
I'm working with vSphere 5.1, SharePoint 2010 and SharePoint 2010 Designer, and I cannot create an External Content Type with the vSphere web services WSDL.
I keep getting a "failed to compile WCF proxy" error. When I enable BCS tracing to determine why the compile failed, I get a "Partial declarations of <element name> must not specify different base classes."