Caching is an optimization feature that can improve the performance of services. When caching is enabled for a service, Integration Server saves the service inputs and results in a local or distributed cache for the period of time that you specify. When Integration Server receives subsequent requests for a service with the same set of input values, Integration Server returns the cached result to the client instead of invoking the service again.

If strict service caching is enabled, Integration Server saves and returns values for fields declared in the service output signature only. If strict service caching is disabled, Integration Server saves and returns the entire output pipeline. 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. Strict service caching is controlled by the watt.server.serviceResults.cache.strict server configuration parameter.

You use Software AG Designer to enable caching for individual services.

Caching can significantly improve response time of services. For example, services that retrieve information from busy data sources such as high-traffic commercial web servers could benefit from caching. Integration Server can cache the results for all types of services: flows, Java services, and C/C++ services.

The goal for caching is to strike the right balance between data concurrency and memory usage. To gauge the effectiveness of your cache, you can monitor its performance by viewing service statistics from the Integration Server Administrator and adjust your caching values accordingly.

You set the controls for caching a service from Designer. For instructions, see webMethods Service Development Help.