HTTP ENDPOINT DECLARATION program that could consume WSDL

HTTP ENDPOINT DECLARATION program that could consume WSDL to know how to communicate with SQL Server. All the SQLXML 3.0 capabilities are available to SQL Server 2005 and SQL Server 2000. But if you have installed SQL Server 2005 on the Windows 2003 Server operating system, additional SOAP functionality can also be exposed directly from the SQL Server engine itself. The reason you need Windows 2003 Server is that in Windows 2003 Server the HTTP stack has been moved into the operating system kernel (this implementation is called HTTP.SYS). SQL Server 2005 Web Services use HTTP.SYS and do not require IIS. This not only allows faster execution of HTTP requests, but allows HTTP to be served from multiple applications running under the operating system, including SQL Server and IIS. You can service HTTP requests from both of them at the same time. Communication with SQL Server through SOAP makes the SOAP protocol an alternative to the TDS protocol. You can define which endpoints will be exposed through SOAP and what protocol these endpoints will use for SQL Server authorization, and use SSL to encrypt the data stream. In addition, you can configure the endpoint with the capability to accept batches of SQL directly. This makes SQL Server truly available to non- Windows clients and available directly over HTTP. No client network libraries are needed. The rest of this chapter will cover SQL Server 2005 s internal SOAP network libraries, although you might notice that most of the SOAP functionality is similar to that exposed in SQLXML 3.0 s ISAPI DLL. The biggest enhancement is that you can produce XML output by running a stored procedure or user-defined function that produces an instance or instances of the XML type as output. HTTP Endpoint Declaration The way that we defined an HTTP endpoint with SQLXML 3.0 was to use either a COM object model that wrote to the IIS metabase and the Windows registry, or to use a graphic user interface that encapsulated this object model. The new functionality is built directly into SQL Server. The information is stored in SQL Server metadata, and the way to define it is to use Transact-SQL. The relevant DDL statements are CREATE ENDPOINT, ALTER ENDPOINT, and DROP ENDPOINT. You can use these DDL statements to define endpoints for protocols other than HTTP (for example, SQL Server Service Broker endpoints), but in this chapter we ll only cover using them to define HTTP endpoints. We ll discuss them here and in the same

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost JSP Web Hosting services

Bookmark the permalink.

Comments are closed.