We have created web service as server (starter activity 'soap event source') process.
How many number of incoming HTTP requests (concurrent i.e.occurring at the same time) that can be handled by this web service ? or How can we define the workload for this process ?
Answer :
Workload can define by setting the following properties in bwengine.tra file:
bw.plugin.http.server.minProcessors
bw.plugin.http.server.maxProcessors
Setting maxProcessors to 100, means upto 100 requests can be accepted concurrently.
Engine.ThreadCount
To improve the ability to execute process instances concurrently, more engine threads are required.
The number of engine threads to be allocated can be set using the property Engine.ThreadCount. The default value is 8.
Engine.StepCount
Set the property, Engine.StepCount, to specify the maximum number of execution steps for a job, unless in a transaction or when the ActivationLimit is set. The default value is 20.
A low value of StepCount results in frequent thread switches. This is an overhead, especially when the number of execution steps for most jobs is high.
bw.plugin.http.client.ResponseThreadPool
To specify the size of the thread pool used by the Request-Reply activity on the web service client side, set the properties:
Workload can define by setting the following properties in bwengine.tra file:
bw.plugin.http.server.minProcessors
bw.plugin.http.server.maxProcessors
Setting maxProcessors to 100, means upto 100 requests can be accepted concurrently.
Engine.ThreadCount
To improve the ability to execute process instances concurrently, more engine threads are required.
The number of engine threads to be allocated can be set using the property Engine.ThreadCount. The default value is 8.
Engine.StepCount
Set the property, Engine.StepCount, to specify the maximum number of execution steps for a job, unless in a transaction or when the ActivationLimit is set. The default value is 20.
A low value of StepCount results in frequent thread switches. This is an overhead, especially when the number of execution steps for most jobs is high.
bw.plugin.http.client.ResponseThreadPool
To specify the size of the thread pool used by the Request-Reply activity on the web service client side, set the properties:
bw.plugin.http.client.ResponseThreadPool
bw.plugin.http.client.ResponseThreadPool.type
As the thread pool is created when the engine starts, use a reasonable number to specify the size of the ResponseThreadPool for your system. A high value results in extra resources being allocated which may never be used.
bw.plugin.http.client.ResponseThreadPool.type
As the thread pool is created when the engine starts, use a reasonable number to specify the size of the ResponseThreadPool for your system. A high value results in extra resources being allocated which may never be used.
