Originally posted by: KVashi

Can anyone explain the significance of setting the Max Concurrent Map Instances=1 in the properties of Integration Flow Designer?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

This determines the number of threads that the launcher uses when running the map - i.e. if you set it to 2 then there can be 2 instances of the map running at the same time (assuming that they don't try to write to the same audit log or trace files etc.).

this is useful for ensuring that you get the best performance out of your server's CPUs and cores.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: TarunB

This setting also overrides server side configuration in the dtx.ini file - MaxThreads and WatchMaxthreads - which I always thought a little odd, i.e. allowing developers to override centralised control parameters.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

The significance of setting this to 1 at the map component is that it is forcing this map component to be single threaded.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange