Enabling caching in deploy anywhere flow services

The caching feature in deploy anywhere flow services enhances integration performance by temporarily storing pipeline data in a local cache. When enabled, caching reduces the need to repeatedly run the resource-heavy operations or retrieve data from external systems, resulting in faster and more efficient processing.

About this task

The caching is not enabled by default.

Note:
  • The caching capability is limited to a single-replica runtime and does not support multi-replica runtimes.
  • Increasing the cache decreases the available memory. If you face memory problems, consider reducing the number of cached elements.
  • Implementing a pre-emptive refill impacts performance, while simultaneously enhancing response time.

For more information on how caching works in flow services, see Caching in Flow services.

Procedure

  1. From the navigation pane, go to Projects and select a project.
  2. Click Integrations > Flow services.
  3. Click Add.
    The Select Flow service type page is displayed.
  4. Select a deploy anywhere flow service.
    The Flow Editor page is displayed.
  5. Click Overflow menu > Settings.
    The Settings dialog is displayed.
  6. Drag the Enable/disable cache switch to the right to enable the cache. The default value is Disabled.
  7. In Cache expire, enter the number of minutes that the flow service results must be stored in cache.
    The default value is 15 minutes. The expiration timer begins when the server initially caches the results. The system does not restart the expiration timer each time it retrieves the results from the cache. The minimum cache expiration time is one minute.
  8. In Preemptive Refill , for Refresh Count, provide the number of invocations, for example, two or four. The webMethods Integration system automatically reruns the service to refill the results in the cache.
  9. Click Done.
    The flow service page is displayed.
  10. Save and run the flow service.
    If the flow service runs successfully, the results are stored in the cache. Otherwise, the results are not cached.