SharePoint Web Services

SharePoint supports interoperability and remote debugging through a series of web services
In Sharepoint, I mean WSS 3.0 (Windows SharePoint Services) and moss.
2007 (Microsoft Office Sharepoint
Server ). There are several ways to program access Sharepoint, such as object model, web services, RPC over
HTTP, and WebDAV. All these methods are based on application needs and have their own advantages and applicability. SharePoint
The RPC protocol is very useful and powerful, especially when adding content to the server, it does have its advantages. Object Model comparison with Web
The Service has more robust features, but it does not support remote operations. Therefore, to use the object model, your code must run on the Sharepoint Server, and you must
Developed in. NET language. There are several different reasons for the remote operation of SharePoint data, such as managing scripts and applications running on client machines that need to access SharePoint content, or non-SharePoint applications in the enterprise need to perform original operations on SharePoint.

SharePoint Web services are built on the object model, exposing a subset of available features in the object model, allowing remote operations on any language and platform that can "consume" Web Services. For most tasks, the web services provided by Sharepoint can meet the requirements,
However, you will also find that some necessary operations in the object model are not available in Web Services.
Service implementation. In this article, we will talk about some out-of-the-box Web applications in wss3 and moss 2007.
And describes how to "consume" them from Java and. net.

Overview of Web Services construction

Me
It won't go too deep into the differences between WSS and Moss. A large number of articles have explained this well. What we need to care about here is the Web
Services. Remember that moss 2007 is built on WSS 3.0. It is built on ASP. NET and runs on IIS (Internet
Information
Server. It is important to have a deep understanding of IIS and ASP. NET, which helps you understand and use Sharepoint. Most of the SharePoint
Web services are included in WSS 3.0, but some of them are included in Moss 2007.
2007 additional features provided, such as more advanced enterprise search features.

SharePoint
Web Services is implemented using ASP. NET web services (asmx ).
Extensions/12/ISAPI "(usually in C:/program files/common files/Microsoft
Shared/Web Server Extensions/12/ISAPI ).
Most of the physical files in services. Management Web for Management Center tools
The service is located in the admisapi folder. In the console, It is a virtual directory named "_ vti_adm. When you create a Sharepoint site
It will contain a virtual directory named "_ vti_bin" to point to this location. IIS does not contain any applications or virtual directories for subsites.
SharePoint ing of the virtual directory _ vti_bin implemented by Sharepoint metadata and httpmodules.

Pair
For any service, you can find a *. WSDL. aspx file, which can generate the Service's WSDL (Web Services Description
Language), A *. Disco. aspx file provides access Discovery Implementation, and an actual *. asmx endpoint file, most of which only contain a reference to the actual
Page specifiers of the SharePoint assembly and type that implement service functions.

Service file type	Description
*. WSDL. aspx (search. WSDL. aspx)	Generate a WSDL (Web Services Description Language) file in SharePoint
*. Disco. aspx (seach. Disco. aspx)	Files for discovery and implementation
*. Asmx (search. asmx)	Web Services endpoint files, most of which only contain a page indicator that references the SharePoint assembly and type that actually implement service functions