WebLogic Server prioritizes work and allocates threads based on an execution model that takes into account administrator-defined parameters and actual run-time performance and throughput.
Administrators can configure a set of scheduling guidelines and associate them with one or more applications, or with particular application components. For example, you can associate one set of scheduling guidelines for one application, and another set of guidelines for other applications. At run time, WebLogic Server uses these guidelines to assign pending work and enqueued requests to execution threads.
To manage work in your applications, you define one or more of the following Work Manager components:
Fair Share Request Class
Response Time Request Class
Min Threads Constraint
Max Threads Constraint
Capacity Constraint
Context Request Class
You can use any of these Work Manager components to control the performance of your application by referencing the name of the component in the application deployment descriptor. In addition, you may define a Work Manager that encapsulates all of the above components and reference the name of the Work Manager in your application's deployment descriptor.
You can define multiple Work Managers—the appropriate number depends on how many distinct demand profiles exist across the applications you host on WebLogic Server. You can configure Work Managers at the domain level, application level, and module level in one of the following configuration files, or by using the WebLogic Server Administration Console. See Using Work Managers to Optimize Scheduled Work in Administering Server Environments for Oracle WebLogic Server.
For information about monitoring and configuring Partition Work Managers in Fusion Middleware Control, see WebLogic Server Partition Work Managers.
Note:
If you are logged into a domain partition, navigate from the Domain Partition menu.
This chapter includes the following section: