Map caching

At design time, set map caching to optimize runtime performance.

Map caching optimizes the runtime performance because the process does not load the compiled map for every iteration of the running of the map. The compiled map is loaded only on the first invocation of the map.

When map caching is set on, any changes that you make to the compiled map are used by the message after you stop and restart the execution group. When map caching is set off, any changes that you make to the compiled map are used by the next message that passes through the message flow.

Set up map caching for each TX Map node to enable individual control for each map node instance. Set map caching on in the Basic tab under Properties in the IBM® Integration Toolkit.

Even after a map is cached, the physical file in the path for the cached map must exist at run time.

A TX Map node can use a map that is cached by a different node if the TX Map node specifies the exact path and name of the cached map.

You can enable RUN map caching in the /runtime/RUN Maps/RunMapMaxCacheNum path of the config.yaml configuration file. Set RunMapMaxCacheNum to the maximum number of maps to cache.