Using a cache to improve performance for custom policy retrieval from WebSphere Service Registry and Repository in WebSphere ESB
From the developerWorks archives
Date archived: January 3, 2017 | First published: June 24, 2009
When developing a custom mediation to retrieve custom metadata, such as a policy from IBM® WebSphere® Registry and Repository, the number of requests can become very large and could dramatically increase the resources needed. One way to reduce the load and increase response time is to use a cache. This article shows how you can extend a mediation primitive deployed in WebSphere Enterprise Service Bus (ESB) to add a cache support This content is part of the IBM WebSphere Developer Technical Journal.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.