When caching is enabled for a service, what Integration Server stores in and returns from the cache depends on whether strict service caching is used. The value of the watt.server.serviceResults.cache.strict server configuration parameter determines whether strict service caching is in use.

In strict service caching, Integration Server caches and returns values for the parameters defined in the service output signature only. Strict service caching is enabled when watt.server.serviceResults.cache.strict is set to true.

When strict service caching is disabled, Integration Server caches values for the defined service signature and the entire output pipeline. When Integration Server uses cached results, Integration Server returns the entire cached output pipeline from the previous service invocation. The pipeline includes the output fields explicitly defined in the cached service, as well as any output fields produced by earlier services in the flow. That is, Integration Server merges the entire output pipeline from the cache entry into the pipeline. This may result in cached pipeline values overwriting the value of fields that are not declared in the service output signature. Caching the entire output pipeline may consume large amounts of memory and disk space. Strict service caching is disabled when the watt.server.serviceResults.cache.strict is set to false, which is the default.