How to enable Multi-Thread Server option for JMS Receiver, AFTER upgrading to 188.8.131.52/184.108.40.206+ ?
Last updated on NOVEMBER 08, 2017
Applies to:Siebel CRM - Version 220.127.116.11 SIA  and later
Information in this document applies to any platform.
This document describes configration steps one needs to perform to enable new Multi-Thread (MT) Server option for "JMS Receiver" Siebel Server component AFTER upgrade to Siebel Fix Pack 18.104.22.168+/22.214.171.124+ from previous releases.
As it is stated in the product guide: Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport > Configuring the EAI JMS Transport > About the JMS Receiver > About Multithreading in the JMS Receiver:
A new Siebel Server component type, EAIJMSRcvr (on which the "JMSReceiver" server component is based on) has been defined for this purpose.
In previous versions, it was single threaded and ran in the background.
Like any other batch component, the JMS Receiver process starts automatically when the Siebel Server is started
When a JMS Receiver task is started, a main task and several worker threads are created, whose number depends on the MinWorkQThreads and MaxWorkQThreads parameters.
In effect, the ReceiveDispatchSend operation (or any method specified) is now called by multiple threads in the same task.
Previously, a single sequential call to the ReceiveDispatchSend method was made in a single process.
Now, the same operation happens in parallel. The thread parallelism effectively increases scalability while limiting CPU load and memory utilization.
NOTE: This new JMS Receiver definition is automatically enabled with NEW installation of Siebel CRM 126.96.36.199/188.8.131.52+. So this manual configuration is not necessary.
To re-iterate the message of this document:
If you install 184.108.40.206/220.127.116.11 and then configure the Gateway and Enterprise for the first time, this will probably create the new component.
If there is an existing Gateway with an existing Enterprise definition, applying the 18.104.22.168/22.214.171.124 Fix Pack will NOT change the component definitions in the enterprise and you will manually need to create the component as described in the document.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms