When Are Cached Results Used?
Integration Server returns cached service results when caching is enabled, results exist in cache, and one of the following is true:
The service has defined input and the runtime input matches the cached input exactly. It is recommended that a cached service has input parameters.
The service has no defined input.
When a cached service has declared input parameters, at run time Integration Server scopes the pipeline down to only the declared input parameters of the service. Integration Server compares the scoped-down inputs to the previously stored copy of the inputs.
If a cached entry exists with input parameters that have the same values, Integration Server returns the cached results from the previous service invocation. If strict caching is enabled, Integration Server returns values for parameters declared in the service output signature only. If strict caching is disabled, Integration Server returns the entire output pipeline, including values for the declared output parameters.
Pipeline Inputs Are Compared to the Cached Copy at Run Time
If a cached entry with input parameter values that are identical to the current invocation does not exist in the cache, Integration Server executes the service and stores the results in the cache.
When a cached service does not have input parameters (for example, a date/time service) and previous results do not exist in the cache, at run time Integration Server executes the service and stores the results. On subsequent service executions, Integration Server uses the cached results. Integration Server returns the cached results until the cache expires. Because there is no input signature, Integration Server does not have anything to compare (either from the cache or from the current service invocation). Integration Server does not use the run-time pipeline for the current service invocation.
Important:
If a cached service input signature includes a Document Reference or Document Reference List variable and the referenced document type changes or is modified, you must reset the service cache. If you do not reset it, Integration Server uses the old, cached input parameters at run time until such time as the cached results expire. You can reset the cache from Designer or Integration Server Administrator. For more information about resetting service cache from Integration Server Administrator, see webMethods Integration Server Administrator’s Guide.
