Create and Set Work Managers for OSB Services

Oracle WebLogic Server prioritizes work and allocates threads based on an execution model for deployed applications, components, Web Services , as well as service-level agreement with a feature named Work Managers (WM).

WMs can be configured by administrators, specifying work execution rules, which then be used by the WebLogic server in order to prioritize work and allocate threads for the applications/components.

In Oracle Service Bus (OSB), several transports for proxy and business services provide a configuration option called “Dispatch Policy” that enables a WM to associate a service to prioritize service work.

The following part gives information on WM usage with services.

Creating Work Manager for OSB Service:

 

1. Disable the proxy service associated with Work Manager on Service Bus;

  • Go to Service Bus Console,
  • Open “Operations” drop menu,
  • Click “Smart Search” on the “Configuration” part,
  • Write the service name (use double asteriks, i.e.*ServiceName*) in “Name” area of Smart Search,
  • Click “Search” button.
Creating WorkManager – Cap.1

Creating WorkManager – Cap.1

 

2. Find the proxy service for the related queue;

  • Click proxy service name,
Creating WorkManager – Cap.2

Creating WorkManager – Cap.2

  • Go to “Operational Settings” tab,
  • Click “Create” button to open a new session,
  • Uncheck the check box of “Enabled” on “State” header,
Creating WorkManager - Cap.3

Creating WorkManager – Cap.3

  • Click “Update” button at the bottom of the page,
  • Click “Activate” button to activate the changes,
Creating WorkManager - Cap.4

Creating WorkManager – Cap.4

Creating WorkManager - Cap.5

Creating WorkManager – Cap.5

  • Finally, enter an explanatory comment for this change and click “Submit” button.

 

3. Next step is to create Maximum Threads Constraint and Work Manager for OSB Service on WebLogic Server. In order to do this;

  • Go to “Environments” in WebLogic Console,
  • Select “Work Managers”,
  • Click “Lock&Edit” button,
Capture - 6

Capture – 6

  • Click “New” button to create work manager,
Capture - 7

Capture – 7

  • Select “Maximum Threads Constraint”,
  • Click “Next” button,
Capture - 8

Capture – 8

  • Enter ‘MTC_MyServiceQueuename’ or something to that effect, (This is important as it needs to match the dispatch policy name in the OSB proxy.)
  • The thread count is advised to be set to an initial value of 1 (lowest acceptable) and can be changed during load testing until the optimal setting is found. (value of -1 is unbounded.),
Capture - 9

Capture – 9

  • Check the “osb_cluster” checkbox whether or not this Work Manager is targeted to the OSB cluster,
  • Click “Finish” button,
  • Finally, click “Release Configuration” button. This should not require a restart.
Capture - 10

Capture – 10

 

4. After ‘MTC_MyServiceQueuename’ is being created , it is Work Manager’s turn to be created;

  • Again select Work Managers part, and Click “New” button,
  • This time select “Work Manager” radio button to create work manager,
  • Click “Next” button,
Capture - 11

Capture – 11

  • Write the ‘WM_MyServiceQueuename’ down on the name field,
  • Click “Next” button,
Capture - 12

Capture – 12

  • Check the “osb_cluster” checkbox whether or not this Work Manager is targeted to the OSB cluster,
  • Click “Finish” button.
Capture - 13

Capture – 13

 

5. Now it is important that you find the Work Manager you created in the list, and link your maximum threads constraint to your work manager. To do that;

  • Go to “Environments” in WebLogic Console,
  • Select “Work Managers”,
  • Select the Work Manager you created from the list,
Capture - 14

Capture – 14

  • On the “Configuration” tab, you will see a combo box called “Maximum Threads Constraint”. From that combo box, select your maximum threads constraint name created,
  • Click “Save” button,
  • And click “Release Configuration” button to activate your changes.
Capture - 15

Capture – 15

 

6. Now, return to Service Bus Console, and find the proxy service you disabled before (i.e Step 1);

  • Go to proxy service,
  • Click “Create” button to create new session,
  • Click “Configuration Details” tab,
  • See “JMS Transport Configuration” header, and click “edit” iconon the left (i.e Pencil/Notebook icon),
Capture - 16

Capture – 16

  • Select the work manager you created from “Dispatch Policy” combo box,
  • Click “Last” button, and click “Save” button.
Capture - 17

Capture – 17

  • Go to “Operational Settings” tab,
  • Check “Enabled” check box from “State” part,
  • Click “Update” button at the bottom of the page,
  • Click “Activate” button to activate changes, enter an explanatory comment for this change, and click “Submit” button.
Capture - 18

Capture – 18

 

Tags:

About the Author

S. Cagatay Yigiter is a Middleware Consultant and works onsite at Turk Telekom, Ankara. He daily operates high level, mission critical OSB and SOA domains successfully.

Post a Reply

Your email address will not be published. Required fields are marked *

Top