![]() ![]() ![]() ![]() |
Application: Configuration: Workload
Configuration Options Related Tasks Related Topics
Java EE enterprise applications, Web application modules, EJBs, and RMI applications can specify named Work Managers for use for managing their work requests. This page lists the Work Managers, request classes, and constraints associated with this enterprise application.
A Work Manager defines a set of request classes and thread constraints that manage work performed by WebLogic Server. A request class defines a fair share thread entitlement, a response time goal, or a context policy for a particular class of application request. Thread constraints define the maximum number of threads to allocate for requests, the minimum number of threads to use for resolving deadlocks, and the total number of requests that can be queued or running before WebLogic Server begins rejecting requests.
To associate a global Work Manager to an enterprise application, you must update the
weblogic-application.xml
deployment descriptor file by adding a<dispatch-policy>
element. After you redeploy the application, the Work Manager will be listed in this table.Configuration Options
Name Description Name The name of the Work Manager.
Changes take effect after you redeploy the module or restart the server.
Type The Work Manager component type.
- Create application-scoped Work Managers
- Create application-scoped constraints
- Create application-scoped request classes
- Configure an enterprise application
- Test the modules in an enterprise application
- Work Manager Configuration
- Response Time Request Class Configuration
- Fair Share Request Class Configuration
- Context Request Class Configuration
- Maximum Threads Constraint Configuration
- Minimum Threads Constraint Configuration
- Capacity Constraint Configuration
- Developing Applications for Oracle WebLogic Server
- Using Work Managers to Optimize Scheduled Work
![]() |