Client Considerations When Web Service and Client Are Deployed to the Same Managed Server Overview of WebLogic Web Services Administration Tasks

Invoking Web Services 6-21 For example, if you change the signature of an operation in the new version of the Web service, then the WSDL file that describes the new version of the Web service will also change. In this case, you must regenerate the JAX-WS stubs. If, however, you simply change the implementation of an operation, but do not change its public contract, then you can continue using the existing client application.

6.9 Client Considerations When Web Service and Client Are Deployed to the Same Managed Server

If a Web service and client are deployed to the same Managed Server, and one of the following is true: ■ The Web service clients uses the WebServiceRef annotation, but does not specify a value for the wsdlLocation element. ■ The Web service client uses the wsdlLocation element of the WebServiceRef annotation to refer to the live WSDL location for example, WebServiceRefwsdlLocation=http:xyz.commyService?WSDL , as opposed to a WSDL that is packaged with the Web service application for example, WebServiceRefwsdlLocation=myService.wsdl. Then, when you restart the Managed Server on which the Web service and client are deployed, the Web service client may fail to redeploy, regardless of the deployment order, because the applications are deployed initially in administration mode, and later transition to production mode to accept HTTP requests. In this situation, you must restart the application manually once the server has restarted. If a Web service and client are deployed to the same Managed Server, to avoid this situation, it is recommended that you package the WSDL as part of the Web service application and refer to the packaged version from the WebServiceRef annotation. 6-22 Getting Started With JAX-WS Web Services for Oracle WebLogic Server 7 Administering Web Services 7-1 7 Administering Web Services The following sections describe how to administer WebLogic Web services: ■ Section 7.1, Overview of WebLogic Web Services Administration Tasks ■ Section 7.2, Administration Tools ■ Section 7.3, Using the WebLogic Server Administration Console ■ Section 7.4, Using the Oracle Enterprise Manager Fusion Middleware Control ■ Section 7.5, Using the WebLogic Scripting Tool ■ Section 7.6, Using WebLogic Ant Tasks ■ Section 7.7, Using the Java Management Extensions JMX ■ Section 7.8, Using the Java EE Deployment API ■ Section 7.9, Using Work Managers to Prioritize Web Services Work and Reduce Stuck Execute Threads ■ Section 7.10, Monitoring Web Services and Clients

7.1 Overview of WebLogic Web Services Administration Tasks

When you use the jwsc Ant task to compile and package a WebLogic Web service, the task packages it as part of an Enterprise application. The Web service itself is packaged inside the Enterprise application as a Web application WAR file, by default. However, if your JWS file implements a session bean then the Web service is packaged as an EJB JAR file. Therefore, basic administration of Web services is very similar to basic administration of standard Java Platform, Enterprise Edition Java EE Version 5 applications and modules. These standard tasks include: ■ Installing the Enterprise application that contains the Web service. ■ Starting and stopping the deployed Enterprise application. ■ Configuring the Enterprise application and the archive file which implements the actual Web service. You can configure general characteristics of the Enterprise application, such as the deployment order, or module-specific characteristics, such as session time-out for Web applications or transaction type for EJBs. ■ Creating and updating the Enterprise applications deployment plan. ■ Monitoring the Enterprise application. ■ Testing the Enterprise application. The following administrative tasks are specific to Web services: 7-2 Getting Started With JAX-WS Web Services for Oracle WebLogic Server ■ Configuring the WS-Policy files associated with a Web service endpoint or its operations. ■ Viewing the SOAP handlers associated with the Web service. ■ Viewing the WSDL of the Web service. ■ Creating a Web service security configuration.

7.2 Administration Tools