Hi all, Step 1 of the proposed solution is modified based on the feed backs .
On Tue, Sep 15, 2015 at 11:52 AM, Isuruwan Herath <[email protected]> wrote: > Hi Rajith, > > On Tue, Sep 15, 2015 at 10:19 AM, Rajith Roshan <[email protected]> wrote: > >> Hi all, >> >> *Problem* >> >> In present conditions Governance registry publisher and store can only be >> configured in the same cluster domain. Retrieving the actual resource >> content from the "Cache Backed" registry when resources are submitted for >> indexing can be identified as the bottleneck for this limitation. >> >> So the updated data in the publisher is not available at the store if >> they are in separate cluster domains.This is due to cache registry being >> populated with stale data which are not updated. >> >> Basic flow of resource retrieving for indexing process is shown below . >> >> >> >> >> *Requirement* >> >> Enable governance registry Store and publisher to be configured in >> separate cluster domains . For example configure Publisher in internal >> server and Store in DMZ. >> >> *Proposed Solution* >> >> Requirement is to get the resources from the embedded registry avoiding >> cache backed registry when resources are submitted for indexing. So the >> updated resources will be available which enables publisher and store to be >> configure in separate cluster domains. >> >> Following are the two sub tasks of the proposed solution. >> >> 1. Add the path of the resource to be fetched for indexing as a no >> cache path. >> >> This can be achieved by including the resource path >> as a no cached path in the "registry context". So the resources will be >> directly fetched from embedded registry only for indexing process. >> > > >> 2. Adding a property to the indexing configuration of the >> registry.xml . >> >> This property can be enabled or disabled using >> registry.xml which will enable or disable caching based on the custom >> requirement. When there is no requirement to have Publisher and Store in >> separate cluster domains this property can be set to false. So the >> resources will be fetched from cache registry. If it is set to true >> resources will be fetched from embedded registry. >> >> Suggestions and feed backs are welcome. >> >> Thanks! >> Rajith >> >> -- >> Rajith Roshan >> Software Engineer, WSO2 Inc. >> Mobile: +94-72-642-8350 <%2B94-71-554-8430> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Isuruwan Herath > Technical Lead > > Contact: +94 776 273 296 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Rajith Roshan Software Engineer, WSO2 Inc. Mobile: +94-72-642-8350 <%2B94-71-554-8430>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
