Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Web Services

Before you begin

Before you can use the Administration Console to install, start, and configure a WebLogic Web service, you must develop one. For detailed information and procedures about developing 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.

The WebLogic Web services programming model centers around Java Web Service (JWS) files and Ant tasks that execute on the JWS files. JWS files are Java files that use JWS metadata annotations to specify the shape and behavior of the Web service. Programmers begin creating a Web service by either programming 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 JEE 5 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.

Programmers can pick one of two implementation types when programming a Web service: 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 also very similar. For example, the programming model is essentially the same in that they both use JWS files and metadata annotations.

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.

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.

The following high-level procedure describes the types of administrative tasks you can perform on Web services using the Administration Console.

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. Install the Web service to make its archive or exploded directory known to the Administration Console. See Install a Web service.
  3. Start the Web service so that client applications can begin using it. See Start and stop a Web service. This task also describes how to stop the Web service so that client applications can no longer access it.
  4. Attach a WS-Policy file to the Web service or its operations. WS-Policy files are used to configure message-level security and reliable messaging. See Attach a WS-Policy file to a Web service
  5. Configure the Web service. Basic configuration details of a Web service include the type of implementation (Java class packaged in a WAR file or a stateless EJB packaged in an EJB JAR file), the full name of the Web service, and so on. See Configure Web services.
  6. Configure Web services reliable messaging. See Configure Web service reliable messaging.
  7. Configure message buffering for Web services. When a buffered operation is invoked by a client, the method operation goes on a JMS queue and WebLogic Server deals with it asynchronously. See Configure message buffering for Web services.
  8. Configure Web service atomic transactions and enable interoperability with other external transaction processing systems. See Configure Web service atomic transactions.
  9. Configure Web service persistence. WebLogic Server provides a default Web service persistence store that provides a built-in, high-performance storage solution for Web services. The Web service persistence store is used by advanced features, such as Web services reliable messaging, to support long running requests and to survive server restarts. See Configure Web service persistence.
  10. View the SOAP message handlers associated with the Web service. See View the SOAP message handlers of a Web service.
  11. View the WSDL of the Web service. See View the WSDL of a Web service.
  12. Test the invocation of a Web service. See Test a Web service.
  13. Monitor the activity of the Web service, such as the number of times it has been invoked and the time of the longest invoke. See Monitor Web services.
  14. Monitor the activity of the Web service client. See Monitor Web service clients.
  15. Create the Web service security configuration that is associated with the Web service.

    When programmers created the Web service, they might have used the @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:

  16. If necessary, delete a Web service. See Delete a Web service.
  17. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

Related Topics

Back to Top