Same map in different watches

You can have the same map in different watches. The initiations of map instances of one watch can be configured to be independent from the initiation of map instances of other watches.

For example, you want to process orders based on priority. All orders look alike before processing and are converted to the same output form. Priority orders are placed on one message queue. Normal orders are placed on another queue. This is the same map with different component names and different sources.

You want Priority Orders to run as fast as possible and (if more than one priority order appears at the same time) you want to process them all at the same time. Normal orders can be processed at the same time, as long as there are enough computer resources available to do so. In this case, you configure Priority Orders to have a higher priority than Normal Orders.

You also set unique work files and unique log files, so that Priority Orders will not need to wait for map system resources. If you just keep work files for each map in a different directory, Priority Orders and Normal Orders could run at the same time. However, this would limit Priority Orders instances to run sequentially. It would also limit Normal Orders instances to run sequentially.

Note: If you are using the log file options and are doing this for more than one map, you might want to keep these files for each watch in a separate directory. Although unique log file names are globally unique, they do not contain the name of the map. For example, if you use log files to trigger other maps, keeping these in a separate directory will make sure the logs trigger the correct map instance.