The system store (IQ catalog store) contains a built-in HTTP server that allows you to provide Web services, as well as to access Web services in other databases and over the Internet. You can manage Web services only for system store tables.
Web services define valid URLs and their functionality. Web services commonly facilitate data transfer and interoperability. You create and store Web services in databases; a single database can define multiple Web services. You can define Web services in different databases so that they appear to be part of a single Web site.
Simple Object Access Protocol (SOAP) is the standard used for access, but the built-in HTTP server also lets you handle standard HTTP and HTTPS requests from client applications.
SOAP provides a method for internet communication, between applications such as those written in Java, or a Microsoft .NET language like Visual C#. SOAP messages define the services that a server provides. Actual data transfer generally takes place using HTTP. Any application, such as a client or server, that participates in SOAP communication is called a SOAP node or SOAP endpoint. Such applications can transmit, receive, or process SOAP messages.
SAP Sybase IQ Web services can listen for and handle standard SOAP requests. Web services provide client applications an alternative to such traditional interfaces as JDBC and ODBC. Web services can be accessed from client applications written in a variety of languages and running on a variety of platforms. Even common scripting languages such as Perl and Python provide access to Web services. You create Web services in a database using the CREATE SERVICE statement.
SAP Sybase IQ can also function as a SOAP or HTTP client, permitting applications running within the database to access standard Web services available over the Internet, or provided by other SAP Sybase IQ databases. This client functionality is accessed through stored functions and procedures.
In addition, the term Web services also refers to applications that use the built-in Web server to handle HTTP requests from clients. These applications generally function like traditional database-backed Web applications, but can be more compact and are easier to write as the data and the entire application can reside within a database. In this type of application, the Web service typically returns documents in HTML format. The GET, HEAD, and POST methods are supported.
The collection of Web services within your database together define the available URLs. Each service provides a set of Web pages. Typically, the content of these pages is generated by procedures that you write and store in your database, although they can be a single statement or, optionally, allow users to execute statements of their own. These Web services become available when you start the database server with options that enable it to listen for HTTP requests.
Since the HTTP server that handles Web service requests is embedded in the database, performance is good. Applications that use Web services are easily deployed, since no additional components are needed, beyond the database and database server.