My Oracle Support Banner

How to Configure Work Managers for OSM (Doc ID 1613129.1)

Last updated on MARCH 14, 2018

Applies to:

Oracle Communications Order and Service Management - Version 7.0.3 to 7.2.4 [Release 7.0.0 to 7.2]
Information in this document applies to any platform.
This document only applies to OSM 7.2.2.3.7 (Patch 18598712) and higher.
This document can be used for currently released versions of OSM 7.0.3 and 7.2.0 using the workaround in the Scope section below.

Purpose

This document outlines how to configure work managers in WebLogic for OSM.

Execute queues have been deprecated in WebLogic and fully replaced by work managers.  Work managers provide a number of advantages over the obsolete execute queue configuration.  They are easier to tune which enables the peak performance to be reached more easily than with execute queues and can avoid known execute queue problems that can lead to deadlocks and other issues in high performance cluster environments.

For more information on execute queues and work managers see the following chapters in the WebLogic documentation:

OSM will be updated in the future to configure work managers by default.  For now use the steps outlined in this note to migrate existing installations to work managers.

Note: Migrating to work managers is recommended for all customers regardless of operating system, WebLogic instance configuration (clustered or not) and volume/load of the system.

Scope

To use Work Managers with currently available OSM 7.0.3 and 7.2.0 versions the following workaround must be used.

To set permissions for the patch libraries:

  1. Stop all WebLogic Server domains that have been created from MW_home
  2. Edit the WLS_home/server/lib/weblogic.policy file in a text editor i.e. in our case this file location is:    
    /home/osm/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy
      
  3. Add the following text to the end of the file:
    grant codeBase 
    "file:MW_home/patch_wls1033/patch_jars/*" 

    permission java.security.AllPermission; 
    }; 
       
    For example, 
    grant codeBase 
    "file:/home/osm/Oracle/Middleware/patch_wls1033/patch_jars/*" 

    permission java.security.AllPermission; 
    };
     
  4. Save and close the file.
  5. Restart WebLogic Server domains.

You will need to do this on each managed servers.

Details

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
Purpose
Scope
Details
 How to Update the Work Manager Configuration
 Important Work Manager Configuration Settings
 Name Properties
 The OSM Work Managers
 Minimum Thread Constraint Count Property
 Maximum Thread Constraint Data Source Property
 1. Automatic Configuration of Work Managers
 Bring OSM Offline
 Make the Configuration Changes
 Finalise Configuration
 2. Manual Configuration of Work Managers
 Bring OSM Offline
 Remove Existing OSM Execute Queues
 Create and configure OSM Work Managers
 Maximum Threads Constraint
 Minimum Threads Constraint
 The OSM automation Work Manager
 The OSM XML API Work Manager
 The OSM Task Web Client Work Manager
 The OSM JMS WebService Work Manager
 The OSM HTTP WebService Work Manager
 Finalise Configuration

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