Before you begin
Before you can use the Administration Console to install, start, and configure WebLogic Web Services, you must create one.
The WebLogic Web Services programming model centers around JWS
files and Ant tasks that execute on the JWS files. JWS files are
Java files that use Java Web Service (JWS) metadata annotations (a new
JDK 5.0 feature) to specify the shape and behavior of the Web Service.
Programmers begin creating a Web Service by either programing the JWS
file from scratch, or generating a stubbed-out version from an existing
WSDL file (public contract of the Web Service) and updating it with
their business logic Java code. Programmers then use the
jwsc Ant task to generate, from the JWS file, a
deployable J2EE application or module that represents the Web Service.
These tasks are iterative; programmers keep coding and generating the
Web Service until it works as they want.
As part of this iterative process, programmers also use the Administration Console to test that the generated Web Service deploys and works correctly. Later, administrators perform similar tasks on the completed Web Service, such as installing, starting, and further configuring the Web Service, as described in the sections below.
For detailed information and procedures about creating a WebLogic Web Service, see:
A Web Service is a Java class or a stateless session EJB that contains additional artifacts so that it can be invoked using SOAP. The additional artifacts include 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.
Web Services are deployed as either Web applications or EJBs, depending on their implementation. The Web applications or EJBs can be deployed on their own, or as part of an Enterprise Application. See View installed Web Services for instructions on viewing the Web Services that are currently installed on this Administration Server.
You perform this task only if the Web Service has been previously programmed to use the reliable SOAP messaging or buffering features. See Using Reliable SOAP Messagingand Creating Buffered Web Services for information about programming these features for your Web Service.
When programmers created the Web Service, they might have used
@WssConfiguration JWS annotation to associate a
Web Service security configuration to the service. This associated
Web Service security configuration is used to configure security
features (in addition to those specified in any associated WS-Policy
files), such as whether to use X.509 certificates to establish
identity or use a password digest in a SOAP message.
See the following tasks: