Database Reference
In-Depth Information
Database
Tuning of the Oracle database is out of the scope for this topic; however, some of the
relevant steps for tuning that can be performed as part of SOA Suite tuning are listed
in this section. Since SOA Suite is an application running on a J2EE container such
as WebLogic, it requires a database for storing meta data. Monitoring and tuning the
database associated with SOA Suite provides optimum performance for SOA Suite
container and your BPEL composite application.
• Ensure that the initial connection pool and max connection pool are the
same. Use a large number for connection pools to avoid running out of
database connections.
• Use GridLink database source for Oracle RAC connectivity instead of multi
pools. Please refer to Chapter 10 , Architecting High Availability for Busi-
ness Services , for details.
• Disable database connections verifications, testing, and profiling.
• Enable statement caching. This improves SOA Suite performance by
caching executable statements that are used repeatedly in the database.
Dehydration store
The Oracle SOA Suite saves all the BPEL process statuses in dehydration database
tables. The dehydration tables are part of SOA_INFRA schema and created initially
during installs as part execution of RCU.
Over a period of time, you need to purge the metadata from the dehydration store
to manage the growth of the database. Oracle provides a default purge script for de-
leting data which is located in {RCU_HOME}/rcu/integration/soainfra/sql/
soa_purge , however, you need to delete additional data to improve the performance
and manage the database growth.
The database schema ddl can be found at {Oracle SOA Install direct-
ory}\rcu\integration\soainfra\sql\bpel . You can write SQL statements
to delete or update data in dehydration tables. Please refer to Chapter 5 , Test and
Troubleshoot SOA Composites , for further details on dehydration.
Search WWH ::




Custom Search