What is the relationship between llserver.exe threads and the CWS webservice on IIS 8.5?

Kris Boutilier

Assume I am implementing a client against the CWS API to perform a single run of a node metadata manipulation job against a large number of nodes and that the client will be backed against an instance of Content Server 10.5 exclusively reserved for running this job. 

I would like to use a producer/consumer pattern to achieve parallelism. If I configure llserver.exe for 32 threads in opentext.ini am I correct in thinking that I should limit myself to 32 consumer threads in my CWS client, and that to achieve more parallelism I would need to stand up additional server instances, otherwise the additional connections from the consumer threads will simply queue in IIS?

Or is the CWS API implemented as a stand-alone Content Server engine itself, entirely separate from the llserver.exe , and that I can continue to increase the number of parallel connections until I begin to hit the resource limit of the server that is hosting each CWS interface?

Thanks in advance for any input.
Kris Boutilier

Kyle_Swidrovich

Hi Kris,

Each CWS request is packaged and sent over to Content Server (llserver.exe) for processing.
That is, there is a one-to-one relationship between SOAP requests hitting the web server and requests hitting Content Server.
For that reason, if you want to avoid queuing, you should limit the number of concurrent connections to the web service to equal the available number of Content Server threads.

Cheers,
Kyle