OHI Value-Based Payments
 PreviousHomeNext 
3.1.3 Enable Total Recall (optional)Book Index3.2.2 Configuring Authentication Providers

3.2 Install Application

This section lists the steps that are required to deploy the OHI Components application on the Oracle Fusion Middleware WebLogic Server (WebLogic).

3.2.1 Creating WebLogic Work Managers

By default, WebLogic Server uses the default work manager to handle thread management and perform self-tuning. This default Work Manager is used by an application when no other Work Managers are specified in the application’s deployment descriptors. For more information, check the WebLogic documentation on Work Managers.

However, it is recommended to use the following application-specific work managers:

This allows more fine-grained control and work load monitoring of the system.

These work managers are configured by the WLST scripts as part of creating a new domain. For an existing domain the work managers need to be configured manually.
If these work managers are not configured, the system issues warnings at startup like the following example and will use the WebLogic default work manager instead:
<Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name wm/core-work-manager. Dispatch policy wm/core-work-manager will map to the default WorkManager for the application OHI-Vbp-2.x.x.x.x>

Create global work managers through the Administration Console using the steps that are listed in the following table in the given order. Make sure to associate the work managers with the managed servers.

Step

Configuration

Value

1

Minimum Threads Constraint

Name

core-work-manager-min-threads-constraint

Count

16

2

Maximum Threads Constraint

Name

core-work-manager-max-threads-constraint

Count

16

3

Fair Share Request Class

Name

core-work-manager-fair-share-req-class

Fair Share

40

4

Work Manager

Name

wm/core-work-manager

Request Class

core-work-manager-fair-share-req-class

Minimum Threads Constraint

core-work-manager-min-threads-constraint

Maximum Threads Constraint

core-work-manager-max-threads-constraint

Capacity Constraint

None Configured

Ignore Stuck Threads

Checked

5

Minimum Threads Constraint

Name

ws-work-manager-min-threads-constraint

Count

10

6

Maximum Threads Constraint

Name

ws-work-manager-max-threads-constraint

Count

100

7

Fair Share Request Class

Name

ws-work-manager-fair-share-req-class

Fair Share

60

8

Work Manager

Name

wm/ws-work-manager

Request Class

ws-work-manager-fair-share-req-class

Minimum Threads Constraint

ws-work-manager-min-threads-constraint

Maximum Threads Constraint

ws-work-manager-max-threads-constraint

Capacity Constraint

None Configured

Ignore Stuck Threads

Checked

9

Minimum Threads Constraint

Name

ui-work-manager-min-threads-constraint

Count

5

10

Maximum Threads Constraint

Name

ui-work-manager-max-threads-constraint

Count

100

11

Fair Share Request Class

Name

ui-work-manager-fair-share-req-class

Fair Share

50

12

Work Manager

Name

wm/ui-work-manager

Request Class

ui-work-manager-fair-share-req-class

Minimum Threads Constraint

ui-work-manager-min-threads-constraint

Maximum Threads Constraint

ui-work-manager-max-threads-constraint

Capacity Constraint

None Configured

Ignore Stuck Threads

Checked

After configuring work managers, managed servers need to be restarted.

The work manager configuration, like the minimum and maximum threads constraints and the fair share request factors, can be modified at any time in WebLogic Admin Console as is required, for example to increase the number of threads used for task processing.

This largely depends on hardware capacity, system configuration and the load characteristics and typically requires a thorough understanding of the system's performance.

 PreviousHomeNext 
3.1.3 Enable Total Recall (optional)3.2.2 Configuring Authentication Providers