<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Danesh Kuruppu on Medium]]></title>
        <description><![CDATA[Stories by Danesh Kuruppu on Medium]]></description>
        <link>https://medium.com/@dknkuruppu?source=rss-19ea7691a04f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*w3DA0YPr37lEC7RV.</url>
            <title>Stories by Danesh Kuruppu on Medium</title>
            <link>https://medium.com/@dknkuruppu?source=rss-19ea7691a04f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:02:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dknkuruppu/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Beyond Custom Plumbing: The Strategic Value of Built-In Connectors for Modern Enterprises]]></title>
            <link>https://medium.com/@dknkuruppu/beyond-custom-plumbing-the-strategic-value-of-built-in-connectors-for-modern-enterprises-747cb7ae85fa?source=rss-19ea7691a04f------2</link>
            <guid isPermaLink="false">https://medium.com/p/747cb7ae85fa</guid>
            <category><![CDATA[integration]]></category>
            <category><![CDATA[enterprise-integration]]></category>
            <category><![CDATA[connectivity]]></category>
            <category><![CDATA[integration-platform]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Danesh Kuruppu]]></dc:creator>
            <pubDate>Sun, 19 Apr 2026 07:12:18 GMT</pubDate>
            <atom:updated>2026-04-19T07:12:18.991Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In an era where speed-to-integration is a competitive advantage, the decision to build versus buy your connectivity layer is no longer a technical footnote — it is a strategic imperative.</em></p><p>Every enterprise has a version of this story. A digital transformation initiative kicks off with ambition and a generous budget. Early milestones are hit. Then, somewhere between month six and month eighteen, the project quietly stalls — not because of a failed strategy or poor leadership, but because of integration. The systems that were supposed to talk to each other simply do not. And the engineering time required to make them do so consumes the runway meant for everything else.</p><p>This is not a new problem. But it is one for which the industry has increasingly clear answers — answers that too many organizations still resist, often in the name of flexibility or customization. The evidence, however, is compelling: enterprises that deploy platforms with robust, purpose-built connectors dramatically outperform those that rely on custom integration code. Not marginally. Dramatically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*OB4MxQBcD4Cy2ciGDglYLA.png" /></figure><h3>The illusion of control</h3><p>There is an enduring belief in enterprise IT that custom-built integrations offer superior control. The reasoning goes: if your team wrote it, your team understands it. You can modify it. You own the behavior. This is not entirely wrong — but it conflates control with understanding. In practice, bespoke connectors become institutional knowledge silos. The developer who wrote the Salesforce-to-SAP sync in 2019 has long since moved on. The logic lives in a GitHub repository that nobody touches except when it breaks — which is usually at the worst possible moment.</p><p>Built-in connectors invert this dynamic. A well-maintained native connector is maintained by a team whose entire mandate is that single integration surface. It absorbs API versioning changes, authentication protocol shifts, and deprecations before they reach your environment. The cognitive load transfers from your team to the platform vendor, whose commercial incentive is to keep that connector working correctly.</p><p><em>Platform in practice — WSO2 Integration Platform</em></p><p><a href="https://wso2.com/integration-platform/connectors/"><em>WSO2 Integration Platform Connector Store</em></a><em> is a concrete illustration of this model at scale. It hosts over 600 pre-built connectors spanning cloud SaaS applications (Salesforce, ServiceNow, Gmail, Amazon S3), technology protocols (File, ISO8583), and database systems — all centrally maintained and importable directly into integration flows via the VS Code extension. Each connector ships with OAuth 2.0 token management, retry-based access token refresh logic, and versioned operation schemas, removing the authentication scaffolding that consumes so much custom development time.</em></p><blockquote><em>“The question is not whether your team can build the connector. It is whether that is the best use of the hours they are billing.”</em></blockquote><h3>Time-to-value is the only metric that matters</h3><p>CTOs operating in today’s landscape are not evaluated on the elegance of their integration layer&#39;s architecture. They are evaluated on outcomes: new revenue channels activated, operational processes automated, and data made accessible to decision-makers. Every week spent building, testing, and debugging a custom connector is a week not spent on those outcomes.</p><p>Enterprise platforms with mature connector libraries — covering the core SaaS stack, ERPs, CRMs, data warehouses, messaging systems, and industry-specific tools — compress the integration phase of a deployment from months to days. This is not marketing language. It is a structural shift in the velocity at which enterprises can respond to change. A company that can integrate a new payment provider in a day has a fundamentally different strategic posture than one that requires a six-week sprint to do the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*t6hsbsRpAIVn9eWNrSsadw.png" /></figure><h3>Security and compliance cannot be an afterthought</h3><p>Perhaps the most underappreciated dimension of the built-in connector debate is security posture. When integration code is custom-written, security practices vary with the developer who wrote it. Token handling, credential rotation, certificate management, and data-in-transit encryption are implemented inconsistently across a portfolio of bespoke connectors. Auditing that portfolio ahead of a SOC 2 review or a regulatory examination is a significant undertaking.</p><p>Purpose-built connectors produced by a platform vendor with enterprise security requirements are, by design, built to a common standard. Credential management follows a unified model. Audit logs are structured and accessible. When a zero-day vulnerability affects an OAuth implementation, the patch is applied once—not across dozens of custom scripts scattered throughout the codebase.</p><p>For CTOs in regulated industries — financial services, healthcare, critical infrastructure — this consistency is not a convenience. It is a risk management imperative. The cost of a single compliance failure or data exposure incident dwarfs any savings from avoiding platform licensing fees.</p><h3>The vendor ecosystem flywheel</h3><p>There is a network effect within a mature connector ecosystem that warrants explicit attention. As a platform’s connector library grows, the cost of adopting new tools within an enterprise decreases. When the next generation of AI-native SaaS tools enters your stack — and it will — an enterprise running a platform with a thriving connector marketplace can evaluate adoption on business merit alone, not on the basis of integration feasibility.</p><p>This is the compounding advantage that is difficult to articulate in a budget presentation but becomes unmistakable over a five-year horizon. The enterprises that will move fastest in 2028 are the ones building that optionality today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*GyCfivApH4rDTM_7VKwJ-w.png" /></figure><blockquote><em>“Integration agility is not a feature. It is the foundation on which every future capability will be built.”</em></blockquote><h3>Choosing the right platform: what to demand</h3><p>Not all connector ecosystems are created equal. Volume of connectors is a vanity metric; the questions that matter are depth, maintenance cadence, and enterprise-grade reliability. CTOs evaluating platforms should demand transparency on connector SLAs, API version coverage, and mean time to remediate when upstream vendors make breaking changes. They should ask for case studies from enterprises in comparable industries — not the sanitized marketing versions, but the operational details.</p><p>They should also evaluate the extensibility story. Even the broadest connector library will have gaps. The platform that wins in the long term is not the one that has covered every possible integration today, but the one whose architecture makes it straightforward to add new connectors — whether built by the vendor, the partner ecosystem, or your own team when genuinely necessary. Platforms like WSO2 Integrator, where connectors operate as reusable, pluggable modules shared across integration projects, demonstrate what that extensibility looks like in practice: one team builds the connector to a legacy protocol, and every other team in the enterprise inherits it immediately.</p><h3>The integration debt reckoning is coming</h3><p>For organizations still running on a patchwork of custom integration scripts, the reckoning is not a matter of if but when. The maintenance burden compounds silently until a critical system upgrade, a vendor API deprecation, or a new compliance requirement forces the issue at exactly the wrong moment. The enterprises that will navigate that moment with composure are those that have already moved to a platform where integration is a managed service rather than a recurring engineering project.</p><p>The case for built-in connectors is not about outsourcing control. It is about redirecting your team’s talent toward the work that actually differentiates your organization. Infrastructure should be boring. Integration should be solved. The platform you choose should make both of those true.</p><p><strong>TL;DR</strong></p><p>Custom integration code feels like control. In practice, it becomes debt — slow to build, expensive to maintain, and brittle under change.</p><p>Built-in connectors shift that burden to the platform, freeing your team to focus on work that actually moves the business forward. The enterprises that treat integration as solved infrastructure — not a recurring engineering project — are the ones that will adapt fastest, scale most efficiently, and outpace competitors who are still rebuilding the same plumbing every few years.</p><p>Stop building connectors. Start building advantages.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=747cb7ae85fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A new book on gRPC — O’Reilly “gRPC Up and Running”]]></title>
            <link>https://medium.com/@dknkuruppu/a-new-book-on-grpc-oreilly-grpc-up-and-running-8317bcfc775f?source=rss-19ea7691a04f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8317bcfc775f</guid>
            <category><![CDATA[grpc]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[cncf]]></category>
            <category><![CDATA[oreilly]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Danesh Kuruppu]]></dc:creator>
            <pubDate>Thu, 20 Feb 2020 17:50:37 GMT</pubDate>
            <atom:updated>2020-02-20T18:06:26.228Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong><em>A new book on gRPC — O’Reilly “gRPC Up and Running”</em></strong></h3><p><em>Building Cloud-Native Applications with Go and Java for Docker and Kubernetes</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/274/0*IgriDHDUOfsiPv21" /></figure><p><em>It’s a great pleasure to announce the release of our new book “gRPC Up and Running”. </em>As the co-author of this book, I would like to share a detailed overview of the book. But before going into that let me explain why we decided to write a book on gRPC protocol.</p><h3>Why a book on gRPC?</h3><p>gRPC is a high-performance interprocess communication protocol based on RPC (Remote Procedure Calls). It is capable of efficiently connecting polyglot services in microservices architecture while providing a rich framework for defining service contracts and data types.</p><p>It is a relatively new technology compared to the REST services and has been there for only years. But it is becoming increasingly popular. The developers and architects who are moving into microservices architecture tend to use gRPC for inter-service communication because it is faster and consumes lesser network and CPU resources.</p><p>When it comes to the availability of the resources to learn about gRPC and the ecosystem around it, Official web site <a href="https://grpc.io/">grpc.io</a> covers the fundamentals and there are many online resources provide different important aspects about gRPC. We thought of bringing all these pieces of information together and provide a comprehensive guide for developers who are trying to build an efficient communication between microservices using gRPC.</p><p>Along with the book, we also provide code samples in different languages. Most of the samples are written in Go and Java languages and we are expecting to extend this to other languages as well soon. You can find the source repo in <a href="https://grpc-up-and-running.github.io/">https://grpc-up-and-running.github.io</a>.</p><h3>What do you get from the book?</h3><p>This book contains eight chapters and every chapter covers a different area of gRPC protocol. All chapters are interconnected with each other. So we are recommending reading it from the beginning. Let me give you a brief introduction to each chapter of the book.</p><h4>Chapter 01: Introduction to gRPC</h4><p>In this chapter, we give an introduction to gRPC and cover what gRPC is, why gRPC is important to inter-service communication. We also talk about the fundamentals of gRPC and compare gRPC with other communication protocols like GraphQL and Thrift. In the end, we mention some of the real-world use cases collected from different resources.</p><h4>Chapter 02: Getting Started with gRPC</h4><p>This is a kind of hands-on session to give a feeling about how to create gRPC service and client, how to build and run them. We provide step by step guidelines for both Go and Java languages in this chapter. In the sample repository(<a href="https://grpc-up-and-running.github.io/">https://grpc-up-and-running.github.io</a>), there are samples for Go, Java, Node.js, and Python languages.</p><h4>Chapter 03: gRPC Communication Patterns</h4><p>Here we talk about four different communication patterns supported in gRPC with diagrams and sample codes. To make it consistent, we explain the pattern using Go code samples. In the sample repository(<a href="https://grpc-up-and-running.github.io/">https://grpc-up-and-running.github.io</a>), we provide samples for Go and Java languages.</p><h4>Chapter 04: gRPC Under the Hood</h4><p>In this chapter, we’ll explore how the gRPC communication flow is implemented, what encoding techniques are used, how gRPC uses the underlying network communication techniques. This is low-level details about how gRPC works.</p><h4>Chapter 05: gRPC Beyond the Basics</h4><p>This covers additional capabilities supported by the various languages to meet requirements such as intercepting incoming and outgoing RPC, handling network delays resiliently, handling errors, sharing metadata between services and consumers. We also provide code samples in Go language in the book and code samples in both Go and Java languages in the sample repository(<a href="https://grpc-up-and-running.github.io/">https://grpc-up-and-running.github.io</a>).</p><h4>Chapter 06: Secured gRPC</h4><p>Here we cover how to secure your gRPC service. Basically how we secure communication channels between microservices and how we authenticate and control access by users of microservices. We discuss security fundamentals to address the challenge of securing the service with code samples in the Go language.</p><h4>Chapter 07: Running gRPC in Production</h4><p>In this chapter, we discuss some important aspects we need to consider when we are running gRPC service in Production like how we can write tests for our gRPC service/client, how we can integrate them with continuous integration tools, how we deploy an application on Docker and Kubernetes. We also discuss how to build a sold observability platform around the gRPC application. Those aspects are not specific to gRPC. We can apply to any service or client implementation.</p><h4>Chapter 08: The gRPC Ecosystem</h4><p>In the final chapter, we explore some projects that are not part of the core gRPC implementation but could be quite useful in building and running gRPC applications.</p><p>Hope this gives you a good understanding of the book. Our key objective is to write a comprehensive book to make life easier for developers and architects, who are new and passionate to learn about gRPC.</p><p>I hope you’ll find this book is useful to get started with the gRPC protocol. Please share your feedback on this book. Your feedback is really important to go forward. If you are interested, please contribute to the sample repository by adding samples in other languages.</p><p>You can purchase the book from all the popular booksellers worldwide including <a href="https://www.amazon.com/gRPC-Running-Building-Applications-Kubernetes/dp/1492058335/">Amazon</a> and <a href="https://www.barnesandnoble.com/w/grpc-kasun-indrasiri/1132647211?ean=9781492058335#/">Barns and Nobel</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8317bcfc775f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create Our Own custom indexer for Wso2 registry indexing]]></title>
            <link>https://medium.com/@dknkuruppu/create-our-own-custom-indexer-for-wso2-registry-indexing-a083cb1f0c4b?source=rss-19ea7691a04f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a083cb1f0c4b</guid>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Danesh Kuruppu]]></dc:creator>
            <pubDate>Wed, 21 Sep 2016 10:16:25 GMT</pubDate>
            <atom:updated>2016-09-21T11:34:51.836Z</atom:updated>
            <content:encoded><![CDATA[<p>In Wso2 registry, we are using apache solr to support registry search feature. To support solr search, all registry resources which are saved in RDBMS, are indexed using periodic task.</p><p>In order to index the resource content, we need to extract the content of the resource. Extracting content of the resource logic varies from resource type. So they have given an extension point to write our own custom logic to create index document of each resource. Steps to create custom indexer are as follows,</p><ul><li>Create maven project and add following dependencies and wso2 maven repository</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cea95344a4fc41e9bc84092b4829e4b7/href">https://medium.com/media/cea95344a4fc41e9bc84092b4829e4b7/href</a></iframe><ul><li>Create a java class implementing indexer interface (org.wso2.carbon.registry.indexing.indexer.Indexer) and override the method getIndexedDocument(). Resource content extracting logic should write here. For example,</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/960661df67db057c513ed3a1ca104693/href">https://medium.com/media/960661df67db057c513ed3a1ca104693/href</a></iframe><ul><li>Add build jar file into &lt;carbon-home&gt;/repository/components/dropins</li><li>Add below configure inside &lt;indexingConfiguration&gt;/&lt;indexers&gt; in registry.xml. (inside &lt;carbon-home&gt;/repository/conf/)</li></ul><blockquote>&lt;indexer class=”org.wso2.carbon.registry.indexer.TextIndexer” mediaTypeRegEx=”application/text\+plain” profiles=”default,uddi-registry”/&gt;</blockquote><p>So that it looks like,</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a2d11e81335d54626971f3b5e6c93037/href">https://medium.com/media/a2d11e81335d54626971f3b5e6c93037/href</a></iframe><ul><li>Start the server, newly added indexer will hit when we add/update resource with the mediatype mapped for the indexer in registry.xml</li></ul><p>Happy Searching !!!!!!!!!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a083cb1f0c4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WSO2 Registry search | FAQ]]></title>
            <link>https://medium.com/@dknkuruppu/wso2-registry-search-faq-6666102b1b94?source=rss-19ea7691a04f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6666102b1b94</guid>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[search]]></category>
            <category><![CDATA[registry]]></category>
            <dc:creator><![CDATA[Danesh Kuruppu]]></dc:creator>
            <pubDate>Wed, 20 Jul 2016 17:27:54 GMT</pubDate>
            <atom:updated>2020-05-28T06:59:50.838Z</atom:updated>
            <content:encoded><![CDATA[<h4>Question 01: How registry indexing works?</h4><p>The registry indexing task is running in the background to collect the latest updates of the registry.</p><ul><li>We read the REG_LOG table periodically to get the latest updates.</li><li>We get the latest content of the updated resources from the registry and create SOLR indexes and add it to the indexed data.</li></ul><p>Since this is a period task, There is no end state of it.</p><h4>Question 02: Where is indexed data stored in the WSO2 server. Can we change the data storage location?</h4><p>By default, indexed data is stored in the &lt;CARBON-HOME&gt;/solr/data directory. we can change the location by changing the below configure in solrconfig.xml inside &lt;CARBON-HOME&gt;/repository/conf/solr/registry-indexing/conf/ directory.</p><blockquote>&lt;dataDir&gt;./repository/solr/registry-index/data&lt;/dataDir&gt;</blockquote><h4>Question 03: How can we re-index the data we stored in the server.</h4><ol><li>Delete the ‘solr’ directory inside &lt;CARBON-HOME&gt; directory.</li><li>Change the name (e.g. lastaccesstime to lastaccesstime_1) of the file in the registry which tracks the last access time of indexing the resources, by changing the value of the &lt;lastAccessTimeLocation&gt; property in the &lt;G-REG_HOME&gt;/repositiry/conf/registry.xml file as follows.</li></ol><blockquote>&lt;lastAccessTimeLocation&gt;/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime_1&lt;/lastAccessTimeLocation&gt;</blockquote><p>3. Restart the WSO2 server and wait for around 30 minutes. This time duration depends on the number of resources that are there in the registry.</p><h4>Question 04: Can we delete data in REG_LOG table periodically. Is there any deletion logic to apply?</h4><p>REG_LOG table contains all the registry operations performed for every registry resource in the system. This is the only place we can track registry operations performed against the user. So we cannot delete this data unless there is an exceptional scenario where we have lots of data in the table and the query takes lots of time to execute.</p><p>In the case of indexing, we are highly relying on this table. If they need to clean up this table, it is needed to keep the latest record from every resource path in the REG_LOG table. Because if we are going to reindex the data, we need to have at least one reference for every resource path.</p><p>You can try something similar to the below query, please test this before suggesting to the customer.</p><blockquote><em>DELETE n1 FROM REG_LOG n1, REG_LOG n2 WHERE n1.REG_LOG_ID &lt; n2.REG_LOG_ID AND n1.REG_PATH = n2.REG_PATH AND n1.REG_TENANT_ID = n2.REG_TENANT_ID;<br>DELETE FROM REG_LOG WHERE REG_ACTION = 7;</em></blockquote><h4>Question 05: Below query executes frequently in REGISTRY DB. Can we reduce the frequency?</h4><blockquote>SELECT REG_PATH, REG_USER_ID, REG_LOGGED_TIME, REG_ACTION, REG_ACTION_DATA FROM REG_LOG WHERE REG_LOGGED_TIME&gt;:1 AND REG_LOGGED_TIME&lt;:2 AND REG_TENANT_ID=:3</blockquote><p>This is the registry indexing task running in the background to collect the latest updates of the registry. We read the REG_LOG table periodically to get the latest updates. This will not affect the user experience.<br>We can reduce this frequency in registry.xml by changing the value of &lt;indexingFrequencyInSeconds&gt; parameter. If we reduce the frequency, Newly published APIs will not visible in APIM Store immediately. more you reduce the frequency, more time needs to wait for API to appear in the API store.</p><h4>Question 06: In a clustered setup, created and published assets in Publisher are not listed in Store even after sometimes.</h4><p>This is due to the distributed cache issue in the clustered deployment. We need to check the clustering configuration in axis2.xml. The problem here is Store node registry cache is not updated with the latest updates in the Publisher node.</p><p>These assets will appear after we re-index the data stored in the server.</p><h4><strong>Question 07: How do we know whether a particular resource is indexed properly?</strong></h4><p>You can enable debug logs for below two classes,</p><blockquote>org.wso2.carbon.registry.indexing.solr.SolrClient</blockquote><blockquote>org.wso2.carbon.registry.indexing.ResourceSubmitter</blockquote><p>So you see logs are printed in carbon logs for each registry resource. You can also get an idea of whether it finished indexing all the pending resources by enabling these logs. The logs will print only if there is a pending resource to index.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6666102b1b94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embedded vs External(HTTP) Solr Server with WSO2 Server]]></title>
            <link>https://medium.com/@dknkuruppu/embedded-vs-external-http-solr-server-with-wso2-server-98cf44f24964?source=rss-19ea7691a04f------2</link>
            <guid isPermaLink="false">https://medium.com/p/98cf44f24964</guid>
            <dc:creator><![CDATA[Danesh Kuruppu]]></dc:creator>
            <pubDate>Wed, 20 Jul 2016 14:48:53 GMT</pubDate>
            <atom:updated>2016-07-20T14:48:53.563Z</atom:updated>
            <content:encoded><![CDATA[<p>In Governance Registry 5.x.x onwards, we have the capability to connect GREG server with external solr server instead of using embedded solr server shipped with vanilla pack.</p><p>In this post, I am trying to compare pros and cons between using embedded and external solr server in WSO2 Product (GREG, APIM, APPM etc).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*XMWME54fG-l4knhfVQdH5w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98cf44f24964" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Governance Registry with external Solr Server]]></title>
            <link>https://medium.com/@dknkuruppu/governance-registry-with-external-solr-server-bef9d4505230?source=rss-19ea7691a04f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bef9d4505230</guid>
            <category><![CDATA[solr]]></category>
            <category><![CDATA[governance-registry]]></category>
            <category><![CDATA[search]]></category>
            <category><![CDATA[wso2]]></category>
            <dc:creator><![CDATA[Danesh Kuruppu]]></dc:creator>
            <pubDate>Wed, 20 Jul 2016 13:20:56 GMT</pubDate>
            <atom:updated>2016-07-20T13:20:56.915Z</atom:updated>
            <content:encoded><![CDATA[<p>From Governance Registry 5.x.x onward, we can connect external Solr server instead of using Embedded Solr which is shipped with Governance Registry in the vanilla pack. Below diagram illustrate how communication happens between two servers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*jpCE-wqwLzYwmuiBNavVwg.png" /><figcaption>Governance Registry with External Solr Server</figcaption></figure><h3>Steps to configure External Solr Server</h3><ol><li>Download solr server from <a href="http://archive.apache.org/dist/lucene/solr/5.2.1/">http://archive.apache.org/dist/lucene/solr/5.2.1/</a></li></ol><p>NOTE : Recommend to use solr 5.2.1 version. because Governance Registry server is using solrj 5.2.1 client to connect to solr server.</p><p>2. Copy solr core configuration directory(registry-indexing) which is inside &lt;GREG-HOME&gt;/repository/conf/solr/ directory to &lt;solr-home&gt;/server/solr/</p><p>NOTE:</p><ul><li>You need to start GREG server once to enable core configuration (registry-indexing) directory. because this configure directory created when first server startup.</li><li>We did some customizations to the default solr core configuration (in schema.xml). So cannot use default core configuration in solr server.</li></ul><p>3. In registry.xml (inside &lt;GREG-HOME&gt;/repository/conf/ directory), add highlighted parameter under indexingConfiguration as follows.</p><blockquote>&lt;indexingConfiguration&gt; <br> <strong>&lt;solrServerUrl&gt;</strong><a href="http://localhost:8983/solr/registry-indexing"><strong>http://localhost:8983/solr/registry-indexing</strong></a><strong>&lt;/solrServerUrl&gt; </strong><br> &lt;startingDelayInSeconds&gt;60&lt;/startingDelayInSeconds&gt; <br> <br> ……………………..<br> ……………………..<br> &lt;/indexingConfiguration&gt;</blockquote><p>NOTE: Need to change the hostname if you are setting up solr server in different server.</p><p>4. Start the solr server. Go to server location (bin directory) and execute, (./solr start). Following output appears in the terminal when it starts correctly.</p><blockquote>Waiting to see Solr listening on port 8983 [/] <br>Started Solr server on port 8983 (pid=2483). Happy searching!</blockquote><p>5. Go to solr admin console from the url <a href="http://localhost:8983/solr/"><strong>http://localhost:8983/solr/</strong></a></p><p>6. Start the GREG server. If everything works. log entry will appear as follows,</p><blockquote>INFO {org.wso2.carbon.registry.indexing.solr.SolrClient} — Http Sorl server initiated at: <a href="http://localhost:8983/solr/registry-indexing">http://localhost:8983/solr/registry-indexing</a></blockquote><p>Above Steps enables GREG Server to run with External Solr Server. There are many pros and cons with external solr. We will discuss more about this in later posts. Till then,</p><p>Happy Searching !!!!!!!!!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bef9d4505230" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WSO2 Governance Center — Advanced Search Version 02]]></title>
            <link>https://medium.com/@dknkuruppu/wso2-governance-center-advanced-search-version-02-89566e025165?source=rss-19ea7691a04f------2</link>
            <guid isPermaLink="false">https://medium.com/p/89566e025165</guid>
            <category><![CDATA[governance-registry]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[search]]></category>
            <category><![CDATA[solr]]></category>
            <dc:creator><![CDATA[Danesh Kuruppu]]></dc:creator>
            <pubDate>Tue, 19 Jul 2016 03:26:53 GMT</pubDate>
            <atom:updated>2016-07-19T03:26:53.024Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a continuation of last post on <a href="https://medium.com/@dknkuruppu/wso2-governance-center-advanced-search-706c9d09d51a#.6rakuflpj">WSO2 Governance Center — Advanced Search</a>.</p><p>With new Governance Registry 5.3.0 which is going to be released on early next month(August 2016), we are including some additional parameters for the Governance Center. We are including OR and AND search within two search fields and within two values of a same field. This is based on the Apache Solr(Solr 5.2.1).</p><p>Example for the different search criteria as follows,</p><h3>Scenario 01: OR search within two different fields.</h3><p><em>e.g: name:cxf </em><strong><em>OR</em></strong><em> version:2.0.0</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wP5aA2c09zkH--yruxl-0Q.png" /></figure><h3>Scenario 02: AND search within two different fields.</h3><p><em>e.g: name:cxf version:1.0.0</em></p><p>NOTE: Keep space in between the fields, System considers as AND search of those fields.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nvOsLWAK0AqYfzjsofkm0Q.png" /></figure><h3>Scenario 03: OR search within two value of the same field.</h3><p>e.g: <em>name:(cxf </em><strong><em>OR</em></strong><em> BuyMore)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4TRaNDa5uV8sb57-7XZLww.png" /></figure><h3>Scenario 04: AND search within two value of the same field.</h3><p>e.g: <em>name:(uy </em><strong><em>AND</em></strong><em> oy)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ep_sgZpmFAjYHMPt_blHg.png" /></figure><h3>Scenario 05: Complex search query with all combinations</h3><p>e.g: <em>name:(uy </em><strong><em>AND</em></strong><em> oy) </em><strong><em>OR</em></strong><em> lcState:(Development </em><strong><em>OR</em></strong><em> Testing)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cq-A3gwNZ3GplHqmMCVvKA.png" /></figure><p>e.g: <em>name:(uy </em><strong><em>AND</em></strong><em> oy) lcState:(Development </em><strong><em>OR</em></strong><em> Testing)</em></p><p>NOTE: AND search within fields can be done by space in between two fields</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xvwAD78PpRSYd_p2gDNt4g.png" /></figure><p>You can test all these scenarios in Governance Registry 5.3.0 beta pack which is going to release next couple of days.</p><p>Happy Searching !!!!!!!!!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89566e025165" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WSO2 Governance Center — Advanced Search]]></title>
            <link>https://medium.com/@dknkuruppu/wso2-governance-center-advanced-search-706c9d09d51a?source=rss-19ea7691a04f------2</link>
            <guid isPermaLink="false">https://medium.com/p/706c9d09d51a</guid>
            <category><![CDATA[governance-registry]]></category>
            <category><![CDATA[searching]]></category>
            <category><![CDATA[wso2]]></category>
            <dc:creator><![CDATA[Danesh Kuruppu]]></dc:creator>
            <pubDate>Sun, 28 Feb 2016 06:38:42 GMT</pubDate>
            <atom:updated>2016-02-28T06:38:42.248Z</atom:updated>
            <content:encoded><![CDATA[<p>Advanced search operators are query words or symbols that perform special actions in WSO2 Governance Center Store Search. These operators allow you to find what you’re looking for quickly and accurately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*dnvixppKtYboRWFmXZEc6w.jpeg" /><figcaption>Governance Center - Search operators</figcaption></figure><p>Special Notes:</p><ul><li>If you need to search against all assets, you need to do the search query in Store Home page or ALL assets (top-assets page).</li><li>If you need to search against one asset type (e.g.: search only in soap services), you need to do the search query in asset list page of that asset type.</li></ul><p>Technical Reference:</p><p>WSO2 Governance Registry: <a href="http://wso2.com/products/governance-registry/">http://wso2.com/products/governance-registry/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=706c9d09d51a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WSO2 Governance Store — Tracking User Search History]]></title>
            <link>https://medium.com/@dknkuruppu/wso2-governance-store-tracking-user-search-history-ddf3a5fe0aef?source=rss-19ea7691a04f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddf3a5fe0aef</guid>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[governance-registry]]></category>
            <category><![CDATA[searching]]></category>
            <dc:creator><![CDATA[Danesh Kuruppu]]></dc:creator>
            <pubDate>Sun, 28 Feb 2016 04:31:24 GMT</pubDate>
            <atom:updated>2016-02-28T04:34:39.283Z</atom:updated>
            <content:encoded><![CDATA[<p>WSO2 Governance Center is the new concept of Governance Registry which was introduced with 5.x.x on words. We have already released couple of versions of this (5.0.0, 5.0.1, 5.1.0) and we are about to release our next minor release (5.2.0) at the end March 2016. This will be more bug fix release, plus some feature to increase user experience.</p><p>One of the main Feature coming with next release is the capability of tracking user search history in Governance Store UI. To explain bit more about the feature, once user searched for assets in Governance Store, that search query will be automatically stored against the user. So that user can reuse the same query without typing query from the beginning. Below are some couple of screen shots.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svcJXRQFCg8Y4qYO2P0wVg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PaVZDoY-gBEKnxmMkXWMBw.png" /></figure><p>As you can see in above screen shots, user search history is listed down automatically once we type matching word on the search box. You can travels through the suggested history and pick the matching query.</p><p>Addition to above functionality, following capabilities are coming with this feature,</p><ul><li>Search History is maintained per asset type. Means we are keeping search histories for each asset type separately. e.g: search history in <em>REST Services </em>and search history in <em>SOAP Services </em>are different.</li><li>Search History is persisted in configuration registry under the registry path: <em>/_system/config/users/searchhistory/ </em>in separate file per user. So Search History results will not loose after session destroy.</li><li>We can enable or disable this feature anytime by editing the registry resource file <strong>store.json</strong> inside <em>/_system/config/store/configs/</em>. we need to set the <strong>enabled</strong> flag to false to disable the feature. Please see the screenshot for more info.</li><li>We also can configure the max number of search history entries saved in the system by changing the maxCount. We set this to 05 by default. This number is for per asset type.</li></ul><p>Please note that we need to restart the server after we change any of those values.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jn2Lztde8OE5ed76wQQOyA.png" /></figure><p>This feature will be available with Governance Registry 5.2.0 release. Hope you will enjoy searching with new Governance Center.</p><p>Technical Stuff:</p><p>JS Library: <a href="https://twitter.github.io/typeahead.js/">https://twitter.github.io/typeahead.js/</a></p><p>WSO2 Governance Registry: <a href="http://wso2.com/products/governance-registry/">http://wso2.com/products/governance-registry/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddf3a5fe0aef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>