There is an activation agent (bpel.xml) property (since 10.1.3.1), which can be used to control the speed at which the adapter posts messages to BPEL
...
<activationAgents>
<activationAgent partnerLink="JmsDequeuePL" ... >
<property name="minimumDelayBetweenMessages">1000</property>
</activationAgent>
</activationAgents>
</BPELProcess>
</BPELSuitcase>
<activationAgents>
<activationAgent partnerLink="JmsDequeuePL" ... >
<property name="minimumDelayBetweenMessages">1000</property>
</activationAgent>
</activationAgents>
</BPELProcess>
</BPELSuitcase>
The same setting in 11G would be configured as a binding property in the composite.xml the corresponding (inbound) <service>, e.g.
<service name="Inbound">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/demo1#wsdl.interface(SampleInbound_PortType)"/>
<binding.jca config="Dequeue_jms.jca">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/demo1#wsdl.interface(SampleInbound_PortType)"/>
<binding.jca config="Dequeue_jms.jca">
<property name="minimumDelayBetweenMessages">1000</property>
</binding.jca>
</service>
</service>
This setting ensures that there at least will be 1000 milli seconds delay between two consecutive messages being posted to the BPEL process.
Note:
- this setting pertains only to BPEL, and only to one adapter polling thread. If multiple adapter polling threads (e.g. multiple JMS dequeuer threads) have been configured, this setting will control the speed of each thread, not the combined speed.
0 comments:
Post a Comment