I have seen several threads about this, but none seem to directly address or explain how to accomplish what I need. I have a web service called by various clients where they pass in various information that Sonic uses to load specific configuration content for those clients' workflow. The issue is, is that the configuration information for the client has to be queried and loaded for each web service call. Is there a way to cache that information for easy access? What is the recommended way of caching information inside your Sonic environment, so it can be easily queried for improved performance (bear in mind I would want to clear the cache on a configurable schedule)? Thanks.
Hello Adam,
I'm not sure what you mean by "configuration information" but if I needed to cache data in ESB I would do it in a custom java service. You can keep member variables to hold the data you need. You can read it at the first call or at the start of the service... and refresh it anytime you want.
Regards,
Why not simply pass it in a second message part or in the part/message header?
If you are using 8.5 the process context might also be an option.
Regards
Stefan