Reduce the Number of Return Query Columns Use the Aggregate API for Charting Task Statistics

17 Oracle Adapters Performance Tuning 17-1 17 Oracle Adapters Performance Tuning This chapter describes how to tune Oracle Adapters for optimal performance. Oracle Adapters, a component of the Oracle SOA Suite of Applications, provide an integrated view of data and allow multiple applications to be integrated. This chapter contains the following sections: ■ Section 17.1, About Oracle Adapters ■ Section 17.2, Oracle JCA Adapters for FilesFTP ■ Section 17.3, Oracle JCA Adapter for Database Tuning ■ Section 17.4, Oracle Socket Adapter Tuning ■ Section 17.5, Oracle SOA JMS Adapter Tuning ■ Section 17.6, Oracle AQ Adapter Tuning ■ Section 17.7, Oracle MQ Adapter Tuning

17.1 About Oracle Adapters

Oracle technology adapters integrate Oracle Application Server and Oracle Fusion Middleware components such as Oracle BPEL Process Manager Oracle BPEL PM or Oracle Mediator components to file systems, FTP servers, database queues advanced queues, or AQ, Java Message Services JMS, database tables, and message queues MQ Series. For more information on Oracle Adapters, see Oracle Fusion Middleware Users Guide for Technology Adapters.

17.2 Oracle JCA Adapters for FilesFTP

This section describes the various features available for scalability and performance tuning of Oracle File and FTP Adapters.The Oracle File and FTP Adapters provide knobs to throttle the inbound and outbound operations. The Oracle File and FTP Adapters also provide knobs that can be used to tune the performance of outbound operations. The Oracle File and FTP Adapters knobs are described in the following sections: ■ Inbound Throttling Best Practices ■ Outbound Throttling Best Practices ■ Outbound Performance Best Practices 17-2 Oracle Fusion Middleware Performance and Tuning Guide

17.2.1 Inbound Throttling Best Practices

The Oracle File and FTP Adapters provide parameters that can be used to throttle the inbound operations. The table below describes the inbound throttling practices:

17.2.2 Outbound Throttling Best Practices

The Oracle File and FTP Adapters provide parameters that can be used to throttle the outbound operations. The table below describes the outbound throttling practices: Note: For composites with Oracle File and FTP Adapters, which are designed to consume very large number of concurrent messages, you must set the number of open files parameter for your operating system to a larger value. For example, to set the number of open files parameter to 8192 for Linux, use the ulimit -n 8192 command Parameter Type Values Description MaxRaiseSize JCA property name=MaxRaiseSi ze value=100 Default: 10000 ten thousand This parameter defines the maximum number of files that the inbound adapter would submit for processing on each polling cycle. For example, if your inbound directory has 1000 files and the MaxRaiseSize is set to 100, the adapter can increase to 100 files on each polling cycle. Defined in the Inbound JCA File. SingleThreadMode l JCA property name=SingleThre adModel value=true Default: False In this case, the global in-memory queue is used. If the value is true, the poller lists, translates, or publishes files in the same thread. In other words, it does not use the global in-memory queue for publishing. Defined in the Inbound JCA File. ThreadCount JCA property name=ThreadCoun t value=10 Default: -1 In this case, the adapter uses the global thread pool and in-memory queue This parameter enables the Oracle File and FTP Adapters to create their own processor threads rather than depending on the global pool of processor worker threads for processing the enqueued files. This parameter partitions the in-memory queue and each composite application receives its own in-memory queue. If the ThreadCount is set to 0, then the threading behavior is the same as that of the SingleThreadModel. If the ThreadCount is set to -1, then the global thread pool is activated, which is the same as the Default Threading Model. The maximum value that can be set for ThreadCount is 40. Defined in the Inbound JCA File.