Originally posted by: TarunB
You can increase the Maxthreads value to whatever you see fit (within reason), but you should always bear in mind the capacity of the server and what resources are available to WTX. If you set this value too high then you will have too many maps contending for the same (limited) server resources, which will ultimately constrain the performance of your system. Of course, leaving the parameter too low will mean that you are not utilising the full capability of the machine.
Note also the meaning of 'threads'. With MaxThreads at 20, if you have a multi-threaded map which receives many unique trigger points, then it is likely that all of your 20 threads will be consumed by this one map. This could leave other data flows unprocessed for long periods of time. You can then choose to set WatchMaxThreads as needed, or the ultimate override "Max Concurrent Map Instances" in your MSD, which will create a hard limit for that individual watch.
So this becomes a sizing and stress testing exercise. Once you have your WTX system built, you can run various scenarios to determine the optimal throughput of the server, given the configuration of the machine. There are - as you might well be aware already - numerous factors that can affect the performance of a WTX system; server capacity is simply one of them.
Good luck.
Tarun
#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender#DataExchange