Inbound Throttling Best Practices

Oracle Adapters Performance Tuning 17-7 Use check cache on the root descriptortable and any child tables if A is master and B is a privately owned child. If A does not exist, B cannot exist. And if A exists, all of its child tables are loaded as part of reading A.

17.4 Oracle Socket Adapter Tuning

This section describes performance tuning for Oracle Socket Adapter. Performance can be optimized for the Oracle Socket Adapter using Connection Pool if the socket server you are connecting to does not close the socket with each interaction. Connection pool lets you use a socket connection repeatedly, avoiding the overload of creating a new socket for each interaction. In order to enable the connection pool feature for the Oracle Socket Adapter, the KeepAlive connection factory property must be set to True. This connection property can be modified using the Connection Pool tab of Oracle WebLogic Server Administration Console. For instructions on modifying the Oracle Socket Adapter connection pooling, see Configuring Oracle Socket Adapter Connection Pooling in Oracle Fusion Middleware Users Guide for Technology Adapters.

17.5 Oracle SOA JMS Adapter Tuning

This section describes some of the properties that can be set for the Oracle SOA JMS Adapter to optimize performance. See Introduction to the Oracle JMS Adapter in the Oracle Fusion Middleware Users Guide for Technology Adapters for more information.

17.5.1 adapter.jms.receive.threads Property

To improve performance, the adapter.jms.receive.threads property can be tuned for an adapter service. The default value is 1, but multiple inbound threads can be used to improve performance. When specified, the value of adapter.jms.receive.threads is used to spawn multiple inbound poller threads. For example: service name=dequeue ui:wsdlLocation=dequeue.wsdl interface.wsdl interface=http:xmlns.oracle.compcbpeladapterjmstextmessageusingqueuestextm essageusingqueuesdequeue2Fwsdl.interfaceConsume_Message_ptt binding.jca config=dequeue_jms.jca property name=adapter.jms.receive.threads type=xs:string many=false10property binding.jca service Note: One way to prevent merge from performing an existence check for every record, when you know that an insert is required, is to set the primary key to null. Note: The Connection Pool feature is applicable to outbound interactions only. For more information on Socket Adapters, see Oracle JCA Adapter for Sockets in Oracle Fusion Middleware Users Guide for Technology Adapters