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 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-RPC or JAX-WS. 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.
Name Description Deployment Name
The name of the Web Service as it appears in the Deployments table.
The name of the Web Service archive file, either a WAR file or EJB JAR file depending on the Web Service features it implements.
The name of this Web Service. This name appears in the WSDL file that defines the public contract of this Web Service.
The name of this Web Service.
The path to the source of the deployable unit on the Administration Server.
If InstallDir is null, the source path must be an absolute path.
If the source path is relative, it is resolved relative to InstallDir/app.
Use AbsoluteSourcePath to get a fully resolved value.
The path to the deployment plan document on Administration Server.
If PlanDir is null, the plan path must be an absolute path.
If the plan path is a relative path, it is resolved relative to PlanDir.
Use AbsolutePlanPath to get a fully resolved value.
If there is no plan, this returns no plan specified.
The mode that specifies whether a deployment's files are copied from a source on the Administration Server to the Managed Server's staging area during application preparation.
Staging mode for an application can only be set the first time the application is deployed. Once staging mode for an application is set, it cannot be changed while the application is configured in the domain. The only way to change staging mode is to undeploy then redeploy the application.
This attribute overrides the server's staging mode.
The security model that is used to secure a deployed module.
To set this value, you can use the
weblogic.Deployercommand-line tool, the Deployment Assistant in the Administration Console, the WebLogic Scripting Tool (WLST), or some other JMX client.
If you deploy a module using one of the previously mentioned tools and you do not specify a security model value, the module is secured with the security realm's default model ( see RealmMBean SecurityDDModel ).
If you deploy a module by modifying the domain's
config.xmlfile and restarting the server, and if you do not specify a security model value for the module in
config.xml, the module is secured with the
DDOnlymodel, which is the default value of this
In summary, the order of precedence for the value of this attribute is as follows:
If you deploy a module using a runtime deployment utility, the order of precedence is:
The value set by the deployment utility.
The value set as the security realm's default security model.
If you deploy a module by modifying
config.xmland restarting the server, the order of precedence is:
The value that you specify for the module in
The default value of this
An integer value that indicates when this unit is deployed, relative to other deployable units on a server, during startup.
Units with lower values are deployed before those with higher values.
- Start and stop a Web Service
- View the Web Service configuration
- View the WSDL of a Web Service
- Monitor a Web Service
- Install a Web Service
- Introducing WebLogic Web Services
- Getting Started With WebLogic Web Services Using JAX-WS
- Getting Started With WebLogic Web Services Using JAX-RPC
- Programming Advanced Features of WebLogic Web Services Using JAX-WS
- Programming Advanced Features of WebLogic Web Services Using JAX-RPC
- Securing WebLogic Web Servcies
- WebLogic Web Services Reference