My Oracle Support Banner

Global Work Manager And Application Scoped Work Managers Not Picking Requests (Doc ID 1460829.1)

Last updated on SEPTEMBER 28, 2020

Applies to:

Oracle WebLogic Server - Version 10.3.5 and later
Information in this document applies to any platform.

Goal

The following document shows a practical approach in how to configure a Global Work Manager.

As per the link mentioned below for Weblogic 11g, it mentions that Work managers are configured from Deployment descriptors or Admin console.

Under head "Understanding Work manager" and "Using Work Managers, Request Classes, and Constraints" sections from this 11g doc

Where as in the link contains for earlier weblogic version the exact same info that is present in the link EXCEPT for the note which says, "Work managers cant be  configured from Admin console"

http://docs.oracle.com/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/work/CreateGlobalWorkManager.html

"Note: You cannot create or configure app-scoped Work Managers using the Administration Console."

Link for 10.3.5 to note teh difference: 
http://docs.oracle.com/cd/E24001_01/apirefs.1111/e13952/taskhelp/work/CreateGlobalWorkManager.html

 

In order to configure global work manager through console with out making any changes to any of the following descriptor files (i.e. adding <dispatch policy> tag to descriptor files) 

 

Then Global Work Manager doesn't work.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.