| |
Web Service: Overview
Configuration Options Related Tasks Related Topics
A Web service is a set of functions packaged into a single entity that is available to other systems on a network. It is implemented using a Java Web Service (JWS) file, which is a Java class that uses JWS metadata annotations to specify the shape and behavior of the Web service.
This page displays the general configuration of a deployed Web service, such as the name that appears in the Deployments table of the Administration Console, the name of the WAR or EJB JAR file in which it is packaged, and name that appears in the WSDL that describes the Web service.
Depending on the specific features that a Web service implements, it is packaged as either a WAR or an EJB JAR file. Typically, the Web service archive is packaged and deployed inside of an Enterprise application EAR file, although the Web service can also be deployed stand-alone.
WebLogic Web services come in two flavors, based on the Sun specification that they implement: JAX-WS or JAX-RPC. Although the two types of Web services differ slightly in how they are invoked and the other specifications that they support, the two types are very similar. For example, the programming model is essentially the same in that they both use JWS files and metadata annotations
The Web service contains additional artifacts so that it can be invoked using SOAP: Web service-specific deployment descriptors, a WSDL file (public contract of the Web service) and data binding components to convert data between its internal Java representation and its external XML representation used in the request and response SOAP messages.
Configuration Options
Name Description Deployment Name Name of the Web service as it appears in the Deployments table.
Module Name Name of the Web service archive file, either a WAR file or EJB JAR file depending on the Web service features it implements.
Service Name Name of this Web service. This name appears in the WSDL file that defines the public contract of this Web service.
|