Table of Contents
- Title and Copyright Information
- Preface
- 1 Top Tuning Recommendations for WebLogic Server
-
2
Performance Tuning Roadmap and Guidelines
-
Performance Tuning Roadmap
- Understand Your Performance Objectives
- Measure Your Performance Metrics
- Monitor Disk and CPU Utilization
- Monitor Data Transfers Across the Network
- Locate Bottlenecks in Your System
- Minimize Impact of Bottlenecks
- Tune Your Application
- Tune your DB
- Tune WebLogic Server Performance Parameters
- Tune Your JVM
- Tune the Operating System
- Achieve Performance Objectives
- Tuning Tips
-
Performance Tuning Roadmap
- 3 Tuning Java Virtual Machines (JVMs)
- 4 Tuning WebLogic Diagnostic Framework and Java Flight Recorder Integration
-
5
Tuning WebLogic Server
- Setting Java Parameters for Starting WebLogic Server
- Development vs. Production Mode Default Tuning Values
- Deployment
- Thread Management
- Tuning Network I/O
- Tuning the Work Manager Maximum Threads Constraint Queue Size
- Optimize Java Expressions
- Using WebLogic Server Clusters to Improve Performance
- Monitoring a WebLogic Server Domain
- Tuning Class and Resource Loading
- SSL Considerations
-
6
Tuning the WebLogic Persistent Store
- Overview of Persistent Stores
- Best Practices When Using Persistent Stores
- Tuning JDBC Stores
- Tuning File Stores
- Using a Network File System
- 7 Database Tuning
- 8 Tuning WebLogic Server EJBs
- 9 Tuning Message-Driven Beans
-
10
Tuning Data Sources
- Tune the Number of Database Connections
- Waste Not
- Use Test Connections on Reserve with Care
- Cache Prepared and Callable Statements
- Database Listener Timeout under Heavy Server Loads
- Disable Wrapping of Data Type Objects
- Advanced Configurations for Oracle Drivers and Databases
- Use Best Design Practices
- 11 Tuning Transactions
-
12
Tuning WebLogic JMS
- JMS Performance & Tuning Check List
- Handling Large Message Backlogs
- Cache and Re-use Client Resources
- Tuning Distributed Queues
- Tuning Topics
- Tuning for Large Messages
- Defining Quota
- Subscription Message Limits
- Controlling the Flow of Messages on JMS Servers and Destinations
- Tuning Applications Using Unit-of-Order
- Using JMS 2.0 Asynchronous Message Sends
-
Using One-Way Message Sends
- Configure One-Way Sends On a Connection Factory
- One-Way Send Support In a Cluster With a Single Destination
- One-Way Send Support In a Cluster With Multiple Destinations
- When One-Way Sends Are Not Supported
- Different Client and Destination Hosts
- XA Enabled On Client's Host Connection Factory
- Higher QOS Detected
- Destination Quota Exceeded
- Change In Server Security Policy
- Change In JMS Server or Destination Status
- Looking Up Logical Distributed Destination Name
- Hardware Failure
- One-Way Send QOS Guidelines
- Client-side Thread Pools
- Best Practices for JMS .NET Client Applications
- Considerations for Oracle Data Guard Environments
- 13 Tuning WebLogic JMS Store-and-Forward
-
14
Tuning WebLogic Message Bridge
- Best Practices
- Changing the Batch Size
- Changing the Batch Interval
- Changing the Quality of Service
- Using Multiple Bridge Instances
- Changing the Thread Pool Size
- Avoiding Durable Subscriptions
- Co-locating Bridges with Their Source or Target Destination
- Changing the Asynchronous Mode Enabled Attribute
- Tuning Environments with Many Bridges
- 15 Tuning Resource Adapters
- 16 Tuning Web Applications
- 17 Tuning Web Services
- 18 Tuning WebLogic Tuxedo Connector
- A Capacity Planning