Getting Started With SharePoint Web Services. Posted by Trent Swanson on Feb 06, 2008. We failed to create the bookmark.
If the behaviour persists please contact us. NOTE: QCon San Francisco - the 9th international software development conference - Nov 16-20, 2015. 100+ expert practitioner speakers, +1,100 attendees, 15 tracks to cover topics driving the evolution of enterprise software development today.
Мечтаете стать стилистом и внести свой вклад в развитие мировой моды? Приблизьте свою месту вместе с красавицей Барби. Скачать игру барби.
Get more details or register now. SharePoint supports interoperability and remote operations through a set of web services, and by SharePoint I am referring to WSS 3. 0 (Windows SharePoint Services) and MOSS 2007 (Microsoft Office SharePoint Server).
There are number of approaches for programmatic access to SharePoint, such as the object model, web services, RPC over HTTP, as well as WebDAV, all of which have their benefits and their place depending on the needs of the application. The SharePoint RPC protocols can be useful and powerful and it certainly has its strengths, especially when it comes to adding content. The object model is much more robust and feature rich than the web services, but it does not offer support for remote operations, so in order to leverage the object model your code must be running on the SharePoint server, and you must be writing. NET code in order to leverage it.
There are a number of different reasons for working with SharePoint data remotely, be it administrative scripts or the need to work with SharePoint content such as tasks in an application running on a client machine, or non-SharePoint applications in the enterprise. The SharePoint web services are built on top of the object model and expose a subset of features available in the object model, and allow for remote operations and the use of any language and platform that supports the consumption of web services. For most tasks the web services that ship in SharePoint are adequate, but you may find needed operations in the object model that have not been surfaced in the web services, which will require extending the web services with a custom web service implementation.
In this article we will take a look at the web services available in WSS3 and MOSS 2007 out of the box, and how to consume them from Java and. NET. Web Services Architecture Overview. I will not go in to the detailed differences between the WSS and MOSS, as there are a number of articles that do a very good job explaining this, only as needed and where related to the web services. Keep in mind that MOSS 2007 is built on top of WSS 3. 0, which is also built on top of ASP.
NET 2. 0 and runs in IIS (Internet Information Server). A solid understanding of IIS and ASP. NET is important, and go long way in working with and understanding SharePoint.
A majority of the SharePoint web services we will discuss are included in WSS 3. 0, but there are a few additional ones that are included in MOSS 2007 to leverage the additional features that ship with it, such as the more advanced enterprise search features. The SharePoint web services are implemented in ASP. NET Web Services (ASMX), and you will find the physical files for most of these web services in the "Microsoft Shared" directory under "web server extensions12ISAPI" typically located at "C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12ISAPI". The admin web service for the Central Administration tool is located in the ADMISAPI folder for which the central administration console contains a virtual directory named "_vti_adm".
When a SharePoint site is created it will contain a virtual directory named "_vti_bin" that points to this location. IIS does not contain any application or virtual directories for subwebs, they do however contain mapping to the _vti_bin virtual directory through SharePoint metadata and HttpModules. For each service you will find a *. wsdl. aspx file that generates the service WSDL (Web Services Description Language), a *. disco.
aspx providing the service discovery implementation, and the actual *. asmx endpoint files, most of which simply contain a page directive referencing the SharePoint assembly and type containing the actual implementation for the service.