Chapter 1: Overview of Web Services in EAServer
Sybase Web Services Toolkit consists of these components:
The basic SOAP engine, which implements SOAP 1.1, embedded in EAServer.
The tools for creating and managing Web services:
Web-based console for administration, monitoring, and deployment of Web services.
Web-based console for UDDI administration, publish/unpublish, and browsing UDDI registries.
An Eclipse plug-in GUI that you can use to:
Design, develop, and deploy Web services to the EAServer environment.
Control deployed Web services running in the EAServer environment.
Monitor incoming and outgoing messages for each Web service using a SOAP inspector.
Generate standalone Java test clients and JSP clients to invoke Web Services deployed to EAServer environment.
Publish and query Web services to or from UDDI registries.
Command line tools for designing, developing, deploying, managing, and securing Web services.
A private UDDI server installed as a J2EE Web application. Access control enables the UDDI user to control access to these basic UDDI data structures: businessesEntity, businessService, bindingTemplate and tModel.
These technologies and tools are collectively referred to as the Web Services Toolkit (WST).
Web Services is installed as part of a standard EAServer installation. If you customize your installation, you will notice that Web services support consists of:
WST Runtime – the basic SOAP engine and Web services infrastructure.
Eclipse based Development Tool – described in Chapter 2, “Using Sybase Web Services Toolkit—an Eclipse plug-in” and Chapter 4, “Web Services Administration.”
Private UDDI Server – described in Chapter 7, “The Private UDDI Server.”
WST provides a number of options for defining a Web service, including:
Creating a Web service from a local or remote WSDL file or Java file – See “Creating Web services from files” and
Creating a Web service from a JAR file – See deploy (2).
Exposing an installed EAServer component as a Web service – See “Other components”.
Creating and deploying a Web service from an implementation class file – See deploy (1).
WST supports the following service styles:
RPC – the body of the SOAP message is an RPC call containing the method name and serialized versions of the parameters. RPC services use the SOAP RPC conventions, and also encoding rules defined in section five of the SOAP specification.
Document –the body of the SOAP message is viewed as an XML document, as opposed to an RPC call. Document services do not use any encoding, but still provide XML-to-Java databindings.
Wrapped – similar to document services, except that rather than binding the entire SOAP body into one big structure, they “unwrap” the body into individual parameters.
To retrieve any WSDL file for a deployed Web service from a Web browser enter the URL of the WSDL in the form http://host:port/collectionName/services/service?wsdl. For example for the canine shelter sample, enter:
|Copyright © 2005. Sybase Inc. All rights reserved.|