1. Deploying and Managing Oracle Access Management on Kubernetes
  2. Installing Oracle Access Management on Kubernetes
  3. Post Installation Configuration
  4. WebLogic Server Tuning

10.3 WebLogic Server Tuning

For production environments, WebLogic Server tuning parameters must be set.

Installing the WebLogic Remote Console Extension

In order to perform the tuning tasks, you must install the latest WebLogic Remote Console extension console-rest-ext-2.4.15.war in the OAM %DOMAIN_HOME%.

To install the extension, perform the following steps:
  1. On the administrative host, download the latest WebLogic Remote Console extension, console-rest-ext-2.4.15.war, from the WebLogic Remote Console GitHub Repository:
    cd $WORKDIR
    wget https://github.com/oracle/weblogic-remote-console/releases/download/v2.4.15/console-rest-ext-2.4.15.war
  2. Run the following command to find the Domain Home:
    kubectl describe domains <domainUID> -n <namespace> | grep "Domain Home:"
    For example:
    kubectl describe domains accessdomain -n oamns | grep "Domain Home:"
    The output will look similar to the following:
      Domain Home:                     /u01/oracle/user_projects/domains/accessdomain
  3. Execute the following command to enter a bash shell in the <domainUID>-adminserver pod:
     kubectl exec -it <domainUID>-adminserver -n <domain_namespace> -- /bin/bash
    For example:
    kubectl exec -it accessdomain-adminserver -n oamns -- /bin/bash
    This will take you inside a bash shell of the pod:
    
[oracle@accessdomain-adminserver oracle]$
  4. Inside the bash shell run the following commands to create a management-services-ext directory:
    mkdir %DOMAIN_HOME%/management-services-ext
    Where %DOMAIN_HOME% is the path returned earlier.
    For example:
    mkdir /u01/oracle/user_projects/domains/accessdomain/management-services-ext
  5. Outside of the bash shell, run the following command to copy the console-rest-ext-2.4.15.war into the container:
    kubectl -n <namespace> cp $WORKDIR/console-rest-ext-2.4.15.war <domainUID>-adminserver:%DOMAIN_HOME%/management-services-ext/
    For example:
    kubectl -n oamns cp $WORKDIR/console-rest-ext-2.4.15.war accessdomain-adminserver:/u01/oracle/user_projects/domains/accessdomain/management-services-ext/
  6. Inside the bash shell, run the following to make sure the console-rest-ext-2.4.15.war was copied:
    ls -l %DOMAIN_HOME%/management-services-ext
    For example:
    ls /u01/oracle/user_projects/domains/accessdomain/management-services-ext
    The output will look similar to the following:
    console-rest-ext-2.4.15.war

Add Minimum Thread Constraint and MaxThreadsCount

  1. Connect to the OAM Administration Server in the WebLogic Remote Console.
  2. In the Home page, select Monitoring Tree
  3. In the left hand navigation menu, select Deployments > Application Management.
  4. Click oam_server.
  5. Click Create Plan and provide the Plan Path as: /u01/oracle/user_projects/domains/accessdomain/Plan.xml and click Done.
  6. In the left hand navigation menu, select Deployments -> Deployment Tasks and check the plan was successfully deployed (Progress: Success).
  7. In the left hand navigation menu, select Deployments > Application Management > oam_server > Deployment Plan (Advanced).
  8. Select the Variable Assignments tab.
  9. Type CTRL + F (menu Edit > Find) and Search for: /weblogic-web-app/work-manager/[name="wm/OAPOverRestWM"]/min-threads-constraint/[name="MinThreadsCount"]/count.
  10. Click the checkbox for that row, and click the Edit button (above the table). Change the following and click Done:
    • Value: 400
    • Operation: replace
  11. Type CTRL + F (menu Edit > Find) and Search for: /weblogic-web-app/work-manager/[name="wm/OAPOverRestWM"]/max-threads-constraint/[name="MaxThreadsCount"]/count.
  12. Check the checkbox for that row, and click the Edit button (above the table). Change the following and click Done:
    • Value: 1000
    • Operation: Replace
  13. In the left hand navigation menu, select Deployments > Application Management.
  14. Click the checkbox in the oam_server row, and click Update/Redeploy and select Redeploy - Deployment Source and Plan on Server. Click Done.
  15. In the left hand navigation menu, select Deployments -> Deployment Tasks and check the plan was successfully deployed (Progress: Success).
  16. To check that the values have been updated, access the Oracle Enterprise Manager Fusion Middleware Control console, and perform the following steps:
    • From the WebLogic Domain drop-down menu, select System MBean Browser.
    • Click the Search icon, and search for the MBean wm/OAPOverRestWM.
    • In the left hand menu, expand MinThreadsConstraintRuntime > MinThreadsCount, and check the Count value is 400.
    • In the left hand menu, expand MaxThreadsConstraintRuntime > MaxThreadsCount and check the Count value is 1000.

oamDS DataSource Tuning

  1. Connect to the OAM Administration Server in the WebLogic Remote Console.
  2. Click Edit Tree and in the left pane of the console, expand Services > Data Sources > oamDS. In the right hand pane click the Connection Pool tab.
  3. Change Initial Capacity, Maximum Capacity, and Minimum Capacity to 800.
  4. Click Save.
  5. Click the Shopping Cart in the top right of the console, and click Commit Changes.