Using Web services and EAServer, you can take advantage of SOAP, WSDL, and UDDI. These protocols enable you to use third-party components called Web services, which are invoked from application providers. A Web service contained in EAServer can be invoked remotely over HTTP and HTTPS protocols. The Web service object has methods or end points that provide the business logic of the Web service being invoked. Methods are called using SOAP, and the client calling these methods is said to consume the Web service. WSDL describes the service and can be used in client applications. You can also publish business and service information to a UDDI registry site on the Web and make your Web service available to other users. SOAP provides a platform and language-neutral way to access these services.
With SOAP, WSDL, and UDDI, collaboration between business partners is easier because interfaces between applications become standardized across platforms.
Web services can be embedded in Sybase’s Web container environment. Web services supports these standards:
SOAP 1.1 – see “SOAP 1.1”.
WSDL 1.1 – see “WSDL 1.1”.
JAX-RPC 1.0 – see “JAX-RPC 1.0”.
SAAJ 1.1 – see “SAAJ 1.1”.
JAXP 1.1 – see “JAXP 1.1”.
UDDI 2.0 – see “UDDI 2.0”.
