Database Reference
In-Depth Information
Tuning
the
underlying
WebLogic
Application Server
The second level of tuning is done at the application server level. Tuning the ap-
plication server will not only improve the overall messaging performance, but also
other factors like reliability, manageability of transactions, and faster velocity of
Message Driven Beans (MDB)
.
In this section, you will learn how to tune Oracle WebLogic Server, which serves
as the backbone of your SOA infrastructure for:
•
Tuning transactions and timeouts
•
Logging, I/O, and connection buffering
•
Data source connection availability
•
Thread allocation
•
Resource adapter connection pools
•
EJBs and SOA Infra deployments
Tuning transactions and timeouts
Handling transaction timeouts is one of those tasks that are generally left to the
last moment. However, on the SOA infrastructure where composite applications
may be involved in transacting with numerous endpoints, good timeout handling
is critical. Managing response times is directly linked to your system's
Quality
of Service (QoS)
. Badly behaved external systems may go offline and leave the
WebLogic Server threads locked or overloaded systems may stall, causing a net-
work client to block indefinitely. For these and numerous other reasons, it is ab-
solutely necessary to detect and handle network timeouts where participating cli-
ents are part of a transaction. The matter is further worsened when we have long
running business processes that may even span over multiple days, weeks, or
months.
Composite instances may fail due to timeout errors for various reasons. A typical
instance, running on the Oracle SOA Suite 11g infrastructure, interacts with many
