Producer components

Acting as a producer of Web services, the ASE Web Services Engine uses three components: an HTTP handler, a SOAP handler, and an XML mapper.

Figure 2-2: ASE Web Services Engine as producer

The ASE Web Services Engine consists of three producer components: the HTTP Handler, the SOAP Handler, and the XML Mapper. SOAP communication to and from the ASE Web Services Engine is parsed by the HTTP Handler component. The HTTP Handler communicates with the SOAP Handler, which communicates with the XML Mapper. JDBC communication to and from the ASE Web Services Engine is handled by the XML Mapper.

HTTP handler

The HTTP handler supports HTTP 1.1 and listens for requests sent using the HTTP POST and GET methods. The HTTP handler also supports SSL connections.

NoteDo not use GET HTTP requests. These commands embed all arguments within the URL, which cannot be encrypted. Use POST HTTP, which moves all arguments into the body of the HTTP request and allows the whole contents to be encrypted.

SOAP handler

The SOAP handler supports SOAP 1.2 and processes SOAP requests. The SOAP handler also generates WSDL files describing Web services.

XML mapper

The XML mapper encodes relational data, returned from Adaptive Server Enterprise through JDBC, into XML that complies with the SQLX standard. The XML mapper also generates a DTD and an XML schema to describe the data.