Best Practices For Performance Tuning WebLogic Server With E-Business Suite 12.2.x

Best Practices for Performance Tuning
WebLogic Server with E-Business Suite 12.2.x
Kandasamy Nainamalai & Thiagarajan B

Oracle Global Customer Support
November 11, 2016
Copyright 2015, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Internal/Restricted/Highly Restricted
Safe Harbor Statement

The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracles products remains at the sole discretion of Oracle.
Program Agenda
1
12.2 Architecture
Weblogic Admin Console
Tuning Recommendations
Best Practices
Resources
Q&A
Program Agenda
1
12.2 Architecture
Best Practices
Resources
Q&A
12.2 Architecture
12.2 Architecture
Difference between 12.1 and 12.2 Techstack
Application 12.1
Application 12.2
OC4J
WebLogic Server
JSP
WebLogic JSP
BC4J
UIX
Web Listener
Web Listener
10g
BC4J
UIX 11g
BI Publisher
BI Publisher
Forms
Forms
12.2 Architecture
Difference between 12.1 and 12.2 Techstack
Program Agenda with Highlight

1
12.2 Architecture
Best Practices
Resources
Q&A
Weblogic Administration Console

http://myserver.domain:7001/console
10
Weblogic Administration Console
11
Program Agenda
1
12.2 Architecture
Weblogic Server Features
Best Practices
Resources
Q&A
12
Parameters to be tuned
Proactive Monitoring
Data Source Connection Pool Diagnostics
Managed server light-weight mode
Enabling Java Flight Recording
Recommended Patches.
13
Proactive Monitoring Heap Usage
14
Creating Heapdump
It shows current memory allocation details within JVM.
Used when investigating java.lang.OutOfMemory errors or memory leaks.
No overhead involved with this option unless an OutOfMemory error actually occurs.
Strongly recommended for production systems as it is often the only way to further
analyze the problem.
15
Creating Heapdump
For Adminserver
Add the below parameters to s_nm_jvm_startup_properties Context variable:
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<path>
For Managed Servers
Add this to the Configuration --> Server Start -> Arguments section of the managed
server through the WLS Console.
16
Creating Heapdump
Managed server -> Configuration --> Server Start -> Arguments
17
Proactive Monitoring Thread Pool status
18
Proactive Monitoring Thread Pool details
19
Connection Leaks
Release 12.2 employs JDBC data sources to maintain a pool of

connections for database connectivity
They are associated with managed servers (such as oacore and forms)
Connections are checked out, and then returned to the data source when
the request is complete
A connection is said to be leaked if it is not returned, no longer associated

with the connection pool, or otherwise recoverable.
20
Monitoring For Connection Leaks
Services -> Data Sources -> EBSDataSource -> Monitoring
21
22
Data Source Connection Pool Diagnostics
Leaked Connection Count will need the Inactive Connection Timeout (ICT)
parameter to be turned on
By default, it is turned off to cater for the dedicated connections that

need to remain idle within an Oracle E-Business Suite managed server.
Therefore, enabling the Inactive Connection Timeout parameter is only
recommended during the debugging of suspected connection leaks.
Verify the version of OAConnectionPoolManagerImpl.class is
120.7.12020000.2 or higher.
If it is at a lower version then apply Patch 21619282:R12.FWK.C
23
Data Source Connection Pool Diagnostics Level 1 Diagnostics
Navigate to Services -> Data Sources -> EBSDataSource -> Connection Pool -> Advanced
(Expand Arrow).
Update the Inactive Connection Timeout to the desired value in seconds: for example,
a setting of 3600 for one hour.
24
This is the least invasive level, and involves setting the Inactive Connection Timeout
parameter (ICT) Requires Bounce.
Note: This parameter will force-reclaim non-leaked idle connections that are
intentionally reserved/cached and idle for more than the configured.
The ICT value must be set high enough both to allow the data source to reclaim
connections naturally to cycle through two iterations:
First iteration will mark idle connections

Second will reclaim connections marked as idle that have not been returned to the
pool.
Example: If the pool is reaching its maximum capacity every four hours, set the ICT value to
between one and two hours.
25
26
Monitor the system, and after two iterations review the following files
from the run file system.
$EBS_DOMAIN_HOME/servers/servername/logs/managed_server#.log
$EBS_DOMAIN_HOME/servers/servername/logs/managed_server#.out
If multiple managed servers are deployed in different nodes, obtain the

above files for each defined managed server.
A change to the DataSource will affect all target servers (in a cluster).
Within the log files, look for message number BEA-001153.
27
May help when the Level 1 diagnostics stack did not provide sufficient
information.
Provides a more complete stack trace, and redirects the output to a

separate file.
Note: Enabling diagnostic profiling in Oracle E-Business Suite Release 12.2
increases Java memory use, and may have a performance impact on the
managed servers. We recommend using Level 2 in a production
environment only when explicitly requested by Oracle Development or
Support.
28
Services -> Data Sources -> EBSDataSource -> Configuration -> Diagnostics
29
Monitor the system and review the following log from the run file system.
$EBS_DOMAIN_HOME/servers/logs/*datasource.log
As an example, look in the log file for:

#### <EBSDataSource> <WEBLOGIC.JDBC.CONN.LEAK> <Wed Oct 29 15:09:56 PDT
2014> <java.lang.Exception
30
12.2.5 introduces a new -DserverType=wlx start argument for managed

servers
This reduces their memory footprint, by preventing startup of the

Enterprise JavaBeans (EJB), Java EE Connector Architecture (JCA), and Java
Message Service (JMS) services.
Add this to the Configuration --> Server Start -> Arguments section of the
managed server through the WLS Console.
31
Managed server -> Configuration --> Server Start -> Arguments
32
Enabling Java Flight Recording
New feature introduced in 12.2.6 with AD and TXK version 8

Allows enabling Java Mission Control (JMC) and Java Flight Recorder (JFR) n
EBS
Can be used for Java 7 update 40 or later
By default this feature is OFF and it can be enabled via Autoconfig
If enabled below parameters will be added to managed server start script
-XX:+UnlockCommercialFeatures -XX:+FlightRecorder
33
Steps to enable JFR
1. Log in to the Oracle E-Business Suite application tier.
2. Source the Oracle E-Business Suite environment.
3. To enable JFR for the Oracle WebLogic Server managed servers, run the following
command:
$ perl $FND_TOP/bin/txkrun.pl -script=FlightRecorder enable=oacore_server1,forms_server1 -contextfile=$CONTEXT_FILE
4. After running the enable command, restart the managed servers to put the change into
effect.
34
Using Java Mission Control
DEMO
35
Using command-line
After the JFR feature is enabled, JFR recordings can be managed by running the jcmd command
with the desired action appended, plus any applicable options:
jcmd <PID>.<action> [options]
Here are some usage examples, all for a PID of 7000:

To start a recording:
$ jcmd 7000 JFR.start name=MyRecording settings=profile delay=20s duration=2m
filename=/EBS12jfr/myrecording.jfr
To stop a recording:
$ jcmd 7000 JFR.stop name=MyRecording
For all command line options, Please refer to Java Platform, Standard Edition Java Flight
Recorder Runtime Guide
36
Program Agenda
1
12.2 Architecture
Best Practices
Resources
Q&A
37
Best Practices
Managed Servers JVM Tuning
For best response time results, use multiple managed instances instead of
one with higher memory.
oacore_cluster
oacore_server1
4 GB
oacore_cluster
oacore_server1
2 GB
oacore_server2
2 GB
Make sure adequate Physical memory available on the server when you
tune heap space
38
Best Practices
Modifying the JVM properties for AdminServer
When adding more managed servers, it is essential to increase the Admin

Server heap memory to prevent from OutofMemory error.
Steps for modifying AdminServer Heap memory:

Stop the AdminServer using adadminsrvctl.sh script
Modify s_nm_jvm_startup_properties context variable.
Default value is 512 MB. Increase it to 1024 MB.
Run AutoConfig on application nodes.
Start the AdminServer using adadminsrvctl.sh script.
39
Best Practices
Oacore JVM Configuration
Default oacore JVM heap size is 512 MB (roughly supports 50 users)

We recommend to configure 2 GB JVM Heap Space for oacore.
This can roughly support 150 to 200 users depending on usage.
Note: You should always size your systems based on tests using
representative data and workloads for your own environment.
40
Tuning JVM Heap
41
Best Practices
Managed Servers Adding/Removing Managed Servers
Managed server creation/deletion should be done only through the

adProvisionEBS.pl script
Managed servers should not be created from the WebLogic Server

Administration Console.
Steps for adding and removing managed servers are provided on Doc ID
1905593.1
42
Best Practices
Recommended Critical Patches
Apply the critical patches Doc ID 1594274.1

(DB, FMW, Weblogic, Forms and Reports)
Apply the latest AD and TXK patches Doc ID 1617461.1

AD and TXK Delta 8 patches are released.
43
Best Practices
Recommended Tech Stack Upgrades
Database 12.1.0.2 (latest certified version as on date)- Doc ID1926201.1
Fusion Middleware Webtier 11.1.1.9 Doc ID 1590356.1

EBS version 12.2.6 Doc ID 2114016.1
44
Best Practices
Engaging
TXK Inventory Report Note 601736.1

ETCC Code checker output- Note 1594274.1
Found missing patches ; Apply them before logging an SR
AD and TXK Code levels

FMW Logs Note 1362900.1
45
Program Agenda
1
12.2 Architecture
Best Practices
Resources
Q&A
46
Resources
Useful 12.2 Document References (Doc ID 1585889.1)
Managing Configuration of Oracle HTTP Server and Web Application
Services in Oracle E-Business Suite Release 12.2 (Doc ID 1905593.1)
Oracle E-Business Suite 12.2 Data Source Connection Pool Diagnostics (Doc
ID 1940996.1)
Applying the Latest AD and TXK Release Update Packs to Oracle E-Business
Suite Release 12.2 (Doc ID 1617461.1)
Oracle E-Business Suite Applications DBA and Technology Stack Release
Notes for R12.AD.C.Delta.8 and R12.TXK.C.Delta.8 (Doc ID 2159750.1)
47
Resources
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and
Technology Bug Fixes (Doc ID 1594274.1)
Oracle E-Business Suite Release 12.2.5 Readme (Doc ID 1983050.1)
Oracle E-Business Suite Release 12.2.6 Readme (Doc ID 2114016.1)

Oracle E-Business Suite Release 12.2 Technology Stack Documentation
Roadmap (Doc ID 1934915.1)
48
Q&A
49
50

Best Practices For Performance Tuning WebLogic Server With E-Business Suite 12.2.x

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Best Practices For Performance Tuning WebLogic Server With E-Business Suite 12.2.x

Hochgeladen von

Copyright:

Verfügbare Formate

Best Practices for Performance Tuning

WebLogic Server with E-Business Suite 12.2.x

Kandasamy Nainamalai & Thiagarajan B

Safe Harbor Statement

Weblogic Admin Console

Weblogic Admin Console

Program Agenda with Highlight

Weblogic Admin Console

Weblogic Administration Console

Weblogic Administration Console

Weblogic Server Features

It shows current memory allocation details within JVM.

Used when investigating java.lang.OutOfMemory errors or memory leaks.

Release 12.2 employs JDBC data sources to maintain a pool of

A connection is said to be leaked if it is not returned, no longer associated

By default, it is turned off to cater for the dedicated connections that

First iteration will mark idle connections

If multiple managed servers are deployed in different nodes, obtain the

Provides a more complete stack trace, and redirects the output to a

As an example, look in the log file for:

12.2.5 introduces a new -DserverType=wlx start argument for managed

This reduces their memory footprint, by preventing startup of the

New feature introduced in 12.2.6 with AD and TXK version 8

2. Source the Oracle E-Business Suite environment.

Here are some usage examples, all for a PID of 7000:

Weblogic Server Features

When adding more managed servers, it is essential to increase the Admin

Steps for modifying AdminServer Heap memory:

Default oacore JVM heap size is 512 MB (roughly supports 50 users)

Managed server creation/deletion should be done only through the

Managed servers should not be created from the WebLogic Server

Apply the critical patches Doc ID 1594274.1

Apply the latest AD and TXK patches Doc ID 1617461.1

Database 12.1.0.2 (latest certified version as on date)- Doc ID1926201.1

Fusion Middleware Webtier 11.1.1.9 Doc ID 1590356.1

TXK Inventory Report Note 601736.1

AD and TXK Code levels

Weblogic Server Features

Oracle E-Business Suite Release 12.2.6 Readme (Doc ID 2114016.1)

Das könnte Ihnen auch gefallen