Use the doesTaskExist Method

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.