<?xml version="1.0" encoding="UTF-8" standalone="no"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:gd="http://schemas.google.com/g/2005" xmlns:georss="http://www.georss.org/georss" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-27557414</atom:id><lastBuildDate>Thu, 05 Sep 2024 22:40:05 +0000</lastBuildDate><title>Thoughts Integrated</title><description>Just Integration</description><link>http://varadhi.blogspot.com/</link><managingEditor>noreply@blogger.com (Bharath Yadla)</managingEditor><generator>Blogger</generator><openSearch:totalResults>7</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><language>en-us</language><itunes:explicit>no</itunes:explicit><itunes:subtitle>Just Integration</itunes:subtitle><itunes:author>Bharath</itunes:author><itunes:owner><itunes:email>noreply@blogger.com</itunes:email><itunes:name>Bharath</itunes:name></itunes:owner><item><guid isPermaLink="false">tag:blogger.com,1999:blog-27557414.post-7703554348239688279</guid><pubDate>Sun, 12 Oct 2008 06:50:00 +0000</pubDate><atom:updated>2008-10-11T23:50:33.396-07:00</atom:updated><title>Appliance Integration</title><description>Gone are the days of Application Integration - now are the days of Appliance Integration - what is appliance integration and how has it disrupted the traditional way of doing the application integration ….. my next posts will be a series that deal with various aspects of appliance integration like&lt;br /&gt;- What appliances can do to the integration?&lt;br /&gt;- How the integration changes with the usage of appliances?&lt;br /&gt;- What are the best cases that can exploit appliance integration&lt;br /&gt;etc……..&lt;br /&gt;Keep your eyes and minds open….&lt;div class="blogger-post-footer"&gt;Everything that relates to integration - Varadhi (in sanskrit means bridge) - Integration is all about bridging the applications &amp; people together!!!!!&lt;/div&gt;</description><link>http://varadhi.blogspot.com/2008/10/appliance-integration.html</link><thr:total>0</thr:total><author>noreply@blogger.com (Bharath)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-27557414.post-2459092197621466764</guid><pubDate>Sun, 12 Oct 2008 06:49:00 +0000</pubDate><atom:updated>2008-10-11T23:49:54.680-07:00</atom:updated><title>Tibco COE</title><description>For those who are interested in the full white paper [refering to my post below Do you need Integration Competency Center] that I have written for Aalayance - now HCL EAI you can download it from&lt;a href="http://www.hcltech.com/Services/EAS/pdf/Tibco%20CoE.pdf" rel="nofollow"&gt;http://www.hcltech.com/Services/EAS/pdf/Tibco%20CoE.pdf&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;Everything that relates to integration - Varadhi (in sanskrit means bridge) - Integration is all about bridging the applications &amp; people together!!!!!&lt;/div&gt;</description><link>http://varadhi.blogspot.com/2008/10/tibco-coe.html</link><thr:total>0</thr:total><author>noreply@blogger.com (Bharath)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-27557414.post-115757628829928129</guid><pubDate>Wed, 06 Sep 2006 20:54:00 +0000</pubDate><atom:updated>2006-09-06T14:05:36.656-07:00</atom:updated><title>Using API for Middleware......from Mark's Blog..</title><description>I worked with Mark Michelis [I call him The Microsoft Guru... :-) ] while I was providing Integration Strategy for ITRON.... based on the work that we have done together Mark blogged his experience on his blog .....&lt;br /&gt;&lt;br /&gt;I thought it would be good to share the link of that blog....&lt;br /&gt;&lt;br /&gt;&lt;a href="http://mark.michaelis.net/Blog/UsingLineOfBusinessAPIsFromMiddleware.aspx"&gt;&lt;span style="font-size:78%;"&gt;http://mark.michaelis.net/Blog/&lt;span style="font-size:85%;"&gt;UsingLineOfBusinessAPIsFromMiddleware&lt;/span&gt;.aspx&lt;/span&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;Everything that relates to integration - Varadhi (in sanskrit means bridge) - Integration is all about bridging the applications &amp; people together!!!!!&lt;/div&gt;</description><link>http://varadhi.blogspot.com/2006/09/using-api-for-middlewarefrom-marks.html</link><thr:total>0</thr:total><author>noreply@blogger.com (Bharath)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-27557414.post-115696033244020984</guid><pubDate>Wed, 30 Aug 2006 17:51:00 +0000</pubDate><atom:updated>2006-09-06T13:50:21.906-07:00</atom:updated><title>Do you need an Integration Competency Center?</title><description>&lt;div align="left"&gt;&lt;br /&gt;&lt;br /&gt;Having worked on Tibco product development, and extensive solution deployment, I found that an integration governing body is needed for implementing the "right integration solution". Given the complexity of integration solutions and the amout of energies that need to be spent for connecting to various end points, without a doubt I have doubts that anyone would say no for an Integration Competency Center established to leverage and exploit the integration infrastructure. As there are number of projects that are rolled out in the enterprise the more the need for ICC.&lt;br /&gt;&lt;br /&gt;The following picture is from one of the whitepapers that I have written during my tenure at Aalayance Inc., . This indicates what makes a good case for ICC to be established.&lt;br /&gt;&lt;/div&gt;&lt;p&gt;&lt;img style="DISPLAY: block; MARGIN: 0px auto 10px; CURSOR: hand; TEXT-ALIGN: center" alt="" src="http://photos1.blogger.com/blogger/5404/2905/320/COE1.0.png" border="0" /&gt;However this picture would not give any information as how one could determine whether an enterprise needs a competency center or not. This thought has been lingering in my mind for so long and based on the 20 odd integration deployments and strategies that I have put together all through, I tried to abstract the criteria based on which one can tell with a good amount of confidence whether an ICC is needed for an enterprise or not..... &lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;img style="DISPLAY: block; MARGIN: 0px auto 10px; CURSOR: hand; TEXT-ALIGN: center" alt="" src="http://photos1.blogger.com/blogger/5404/2905/320/COE2.png" border="0" /&gt;&lt;/p&gt;&lt;br /&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;The above depicted tool can be used to score against each of the criterion and then if the total score is &gt;24, the enterprise definitely needs an ICC, if it is &lt;20&gt; &lt;p&gt;&lt;span style="font-size:85%;"&gt;Note:----This above depicted model needs to be used with other dimensions to accurately determine the Fit-Gap analysis. &lt;/span&gt;&lt;span style="font-size:85%;"&gt;Aalayance Inc., specializes in doing the same, and we used the same model that was extended multi-dimensionally and used rigoruosly during implementations by Aalayance Inc., [www.aalayance.com]&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;Everything that relates to integration - Varadhi (in sanskrit means bridge) - Integration is all about bridging the applications &amp; people together!!!!!&lt;/div&gt;</description><link>http://varadhi.blogspot.com/2006/08/do-you-need-integration-competency.html</link><thr:total>0</thr:total><author>noreply@blogger.com (Bharath)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-27557414.post-114792448072844105</guid><pubDate>Thu, 18 May 2006 03:54:00 +0000</pubDate><atom:updated>2006-05-17T20:54:40.743-07:00</atom:updated><title>SOA and Middleware...</title><description>Middleware and SOA are very near relatives!!!! for the fact that SOA is primarily built on the principles of exploiting interop.&lt;br /&gt;&lt;br /&gt;Historically if you look at the way the apps have changed the face, they have traditionally grown from monolithic to component based applications. Similarly interop traditionally started with Remote calls and grew to completely transparent way of executing.&lt;br /&gt;&lt;br /&gt;With the explosion of internet and the W3C stds - it was made possible to exploit the true COMPONENT based architecture (which in my opinion has taken the shape of SOA - with service being self-executable component that can serve a business function).&lt;br /&gt;&lt;br /&gt;Since the major problem that is solved using middleware is to transform and transport the data across applicatons, using SOA design patterns can easily leverage the middleware. However, having said that, to run a predictive business, any enterprise will have to leverage "Event Generation" and "Event Analysis" - which can be easily achieved through Event Driven architecture.&lt;br /&gt;&lt;br /&gt;--- note: will post Part-2 of this along with some of the major differences between EDA and SOA and how they both can be exploited&lt;br /&gt;&lt;br /&gt;8:48 PM&lt;div class="blogger-post-footer"&gt;Everything that relates to integration - Varadhi (in sanskrit means bridge) - Integration is all about bridging the applications &amp; people together!!!!!&lt;/div&gt;</description><link>http://varadhi.blogspot.com/2006/05/soa-and-middleware_17.html</link><thr:total>0</thr:total><author>noreply@blogger.com (Bharath)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-27557414.post-114713128589595051</guid><pubDate>Mon, 08 May 2006 23:33:00 +0000</pubDate><atom:updated>2006-05-08T16:34:45.906-07:00</atom:updated><title>Capacity considerations for Integration...</title><description>&lt;span name="intelliTxt" id="intelliTXT"&gt;A posting that I have done on the IT tool box reg. the Capacity considerations... thought will be good for sharing...&lt;br /&gt;&lt;br /&gt;bharath.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Hi Satyendra:&lt;br /&gt;&lt;br /&gt;First thing, for the scenarios that you are&lt;br /&gt;implemeting the instrumentation needs to be developed&lt;br /&gt;based on what needs to be measured. Typically every&lt;br /&gt;&lt;a target="_blank" href="http://eai.ittoolbox.com/groups/technical-functional/tibco-l/854733#" style="border-bottom: 0.075em solid darkgreen; text-decoration: underline; padding-bottom: 1px; color: darkgreen; background-color: transparent;" class="iAs"&gt;deployment&lt;/a&gt; is different and metrics defintion should&lt;br /&gt;be done in accordance with the CRP if has been carried&lt;br /&gt;out during the design.&lt;br /&gt;&lt;br /&gt;Now, coming the what part, as you have presented you&lt;br /&gt;those are few generally used metrics, also you may&lt;br /&gt;want to add the round-trip time, time taken by each&lt;br /&gt;component during the process execution, through put,&lt;br /&gt;you may also want to capture the waist-point for the&lt;br /&gt;same so that you have the inputs on how you can scale&lt;br /&gt;up the solution as such.&lt;br /&gt;&lt;br /&gt;Coming the stress, as per your definition, the&lt;br /&gt;throughput rate should give you the details of how&lt;br /&gt;many messages can be queued [this again depends on&lt;br /&gt;your design choices you might have made]&lt;br /&gt;&lt;br /&gt;Coming, to TIBCO, TIBCO cannot give any metrics which&lt;br /&gt;are specific to your deployment scenarios, it can&lt;br /&gt;definitely give the metrics about the products - as&lt;br /&gt;you have mentioned ems.. etc., As mentioned above you&lt;br /&gt;need to put the instrumentation as per your need to&lt;br /&gt;tap the metrics.&lt;br /&gt;&lt;br /&gt;Hope this helps,&lt;br /&gt;Cheers,&lt;br /&gt;Bharath.&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;Everything that relates to integration - Varadhi (in sanskrit means bridge) - Integration is all about bridging the applications &amp; people together!!!!!&lt;/div&gt;</description><link>http://varadhi.blogspot.com/2006/05/capacity-considerations-for.html</link><thr:total>0</thr:total><author>noreply@blogger.com (Bharath)</author></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-27557414.post-114678825851119422</guid><pubDate>Fri, 05 May 2006 00:14:00 +0000</pubDate><atom:updated>2006-05-04T17:17:38.513-07:00</atom:updated><title>Welcome!!!</title><description>After working on Integration deployments and componnet based development, initiated the idea of hosting this blog to share across the various experiences that would be useful to the community from integration solutions perspective.&lt;br /&gt;&lt;br /&gt;Open to all the integration folks&lt;div class="blogger-post-footer"&gt;Everything that relates to integration - Varadhi (in sanskrit means bridge) - Integration is all about bridging the applications &amp; people together!!!!!&lt;/div&gt;</description><link>http://varadhi.blogspot.com/2006/05/welcome.html</link><thr:total>0</thr:total><author>noreply@blogger.com (Bharath)</author></item></channel></rss>