7-10 Getting Started With JAX-RPC Web Services for Oracle WebLogic Server
7.8 Using the Java EE Deployment API
In Java EE 5, the J2EE Application Deployment specification JSR-88, described at http:jcp.orgenjsrdetail?id=88
, defines a standard API that you can use to configure an application for deployment to a target application server
environment. The specification describes the Java EE Deployment architecture, which in turn defines
the contracts that enable tools or application programmers to configure and deploy applications on any Java EE platform product. The contracts define a uniform model
between tools and Java EE platform products for application deployment configuration and deployment. The Deployment architecture makes it easier to deploy
applications: Deployers do not have to learn all the features of many different Java EE deployment tools in order to deploy an application on many different Java EE
platform products.
See Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for more information.
7.9 Using Work Managers to Prioritize Web Services Work and Reduce Stuck Execute Threads
After a connection has been established between a client application and a Web service, the interactions between the two are ideally smooth and quick, whereby the
client makes requests and the service responds in a prompt and timely manner. Sometimes, however, a client application might take a long time to make a new
request, during which the Web service waits to respond, possibly for the life of the WebLogic Server instance; this is often referred to as a stuck execute thread. If, at any
given moment, WebLogic Server has a lot of stuck execute threads, the overall performance of the server might degrade.
If a particular Web service gets into this state fairly often, you can specify how the service prioritizes the execution of its work by configuring a Work Manager and
applying it to the service. For example, you can configure a response time request class a specific type of Work Manager component that specifies a response time goal for the
Web service.
The following shows an example of how to define a response time request class in a deployment descriptor:
work-manager nameresponsetime_workmanagername
response-time-request-class namemy_response_timename
goal-ms2000goal-ms response-time-request-class
work-manager
You can configure the response time request class using the Administration Console, as described in Work Manager: Response Time: Configuration in the Oracle Fusion
Middleware Oracle WebLogic Server Administration Console Help.
For more information about Work Managers in general and how to configure them for your Web service, see Using Work Managers to Optimize Scheduled Work in Oracle
Fusion Middleware Configuring Server Environments for Oracle WebLogic Server.
8
Upgrading WebLogic Web Services From Previous Releases to 10.3.x 8-1
8
Upgrading WebLogic Web Services From Previous Releases to 10.3.x
The following sections describe how to upgrade a pre-10.3.x WebLogic Server Web service to run in the Oracle WebLogic Server 11g Release 1 10.3.x Web service
run-time environment:
■
Section 8.1, Upgrading a 9.2 or 10.0 WebLogic Web Service to 10.3.x
