<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Integrating Islands with Landmasses</title>
  <link href="http://www.icmembers.org/blog/zaki/rss/atom10" rel="self"/>
  <link href="http://www.icmembers.org/blog/zaki" rel="alternate"/>
  <id>http://www.icmembers.org/blog/zaki</id>
  <description>Integrating Islands with Landmasses</description>
  <updated>2008-05-15T02:19:05Z</updated>
  <author>
    <name>Danesh Zaki</name>
  </author>
  <entry>
    <title>Will Mashups become Enterprise Grade?</title>
    <link href="http://www.icmembers.org/blog/zaki/2008/5/15/will-mashups-become-enterprise-grade" rel="alternate"/>
    <id>http://www.icmembers.org/blog/zaki/2008/5/15/will-mashups-become-enterprise-grade</id>
    <updated>2008-05-15T02:19:05Z</updated>
    <author>
      <name>Danesh Zaki</name>
    </author>
    <content type="html">
&lt;div&gt;&lt;p&gt;There is a lot of buzz around mashups but most of it relates to users mixing social applications. Will  mashups graduate to becoming enterprise level or will they remain stuck at the user level?&lt;/p&gt;&lt;/div&gt;&lt;div&gt;&lt;p&gt;There has been a lot of buzz around Mashups recently with quite a few vendors offering tools for building mashups quickly and easily. IBM announced &lt;a href="http://www.ibm.com/websphere/smash"&gt;WebSphere sMash&lt;/a&gt; based on &lt;a href="http://www.projectzero.org"&gt;Project Zero&lt;/a&gt;, &lt;a href="http://wso2.com"&gt;WSO2&lt;/a&gt; is providing the &lt;a href="http://wso2.com/products/mashup/"&gt;WS02 Mashup Server&lt;/a&gt;, which has some nifty features for taking simple JavaScript code and building a mashup out of it. But for these tools to enter the enterprise mashups space, there is more expected from them. Any talk of enterprise brings ERP systems such as SAP or Oracle Suite to the fore. And when a mashup building tool looks to provide enterprise mashup building capability, it would probably do well to provide a few adapters to connect to these data sources. This would enable &amp;quot;back-end&amp;quot; applications to be integrated, aggregated and presented as a mashup. Until such time, it would be difficult for enterprise mashups and their builder tools to become common place.&lt;/p&gt;&lt;/div&gt;    </content>
  </entry>
  <entry>
    <title>SOI - A part of the whole?</title>
    <link href="http://www.icmembers.org/blog/zaki/2008/3/18/soi-a-part-of-the-whole" rel="alternate"/>
    <id>http://www.icmembers.org/blog/zaki/2008/3/18/soi-a-part-of-the-whole</id>
    <updated>2008-03-18T00:06:00Z</updated>
    <author>
      <name>Danesh Zaki</name>
    </author>
    <content type="html">
&lt;div&gt;&lt;p&gt;Is SOI a necessary part of SOA? &lt;/p&gt;&lt;/div&gt;&lt;div&gt;&lt;p&gt;I am reviewing integration projects being implemented and notice a difference between projects done earlier and now. Interfaces integrating applications (two or more) are now called as integration services, but perform the same task of moving data across. Apparently, everyone wants to get on to the SOA bandwagon in whatever way possible, which behests the question: is an &lt;em&gt;&lt;strong&gt;&lt;font face="Courier New"&gt;EAI Interface + Service Wrapper = SOI&lt;/font&gt;&lt;/strong&gt;&lt;/em&gt; (Service Oriented Integration)? And, can SOI be considered as a necessary part of SOA?&lt;/p&gt;&lt;/div&gt;    </content>
  </entry>
  <entry>
    <title>REST in B2B Integration</title>
    <link href="http://www.icmembers.org/blog/zaki/2007/12/4/rest-in-b2b-integration" rel="alternate"/>
    <id>http://www.icmembers.org/blog/zaki/2007/12/4/rest-in-b2b-integration</id>
    <updated>2007-12-04T02:52:31Z</updated>
    <author>
      <name>Danesh Zaki</name>
    </author>
    <content type="html">
&lt;div&gt;&lt;p&gt;Is REST an option in B2B integration?&lt;/p&gt;&lt;/div&gt;&lt;div&gt;&lt;p&gt;I was reading on REST as it is getting a lot of attention these days. As I came to know more about it, I was wondering if it could be a good alternative to use for B2B integration over the web. Since it is based on HTTP and other well-known standards, it would be easily understood by trading partners and customers. And it may just help people get out of VANs and proprietary EDI software.&lt;/p&gt;&lt;/div&gt;    </content>
  </entry>
  <entry>
    <title>Is Canonical XML dying?</title>
    <link href="http://www.icmembers.org/blog/zaki/2007/10/5/is-canonical-xml-dying" rel="alternate"/>
    <id>http://www.icmembers.org/blog/zaki/2007/10/5/is-canonical-xml-dying</id>
    <updated>2007-10-05T02:04:24Z</updated>
    <author>
      <name>Danesh Zaki</name>
    </author>
    <content type="html">
&lt;div&gt;&lt;p&gt;Rise of ERP data formats and increasing number of performance related issues have been causing&amp;nbsp; a decline on the use of standards based canonical XML.&lt;/p&gt;&lt;/div&gt;&lt;div&gt;&lt;p&gt;Message formats used for transport have evolved from flat files to basic XML and then to canonical XML based on standards. Recently, there has been a movement to use message formats that come with an ERP product, where it is performing core business operations such as Order Management. ERP data formats are being used for conversing with other applications with the justification that since the central system is the ERP product, all changes can be easily controlled since it would be the source of record.&lt;br /&gt;
&lt;br /&gt;
In my opinion, this is not the right approach as it defeats the principle of loose coupling. There is too much dependancy on the ERP system thereby dragging the architecture back to the days of the monoliths. Rather, the correct approach would be for the organization to revive the use of canonical XML by choosing standards relevant to its business domain e.g NRF-ARTS for Retail, papiNet for paper industry etc. The format can then by customized according to its specific needs.&lt;/p&gt;
&lt;p&gt;From an industry standpoint, performance for large canonical messages continues to be an issue. Though workarounds such as compression, segmentation etc exist, they remain just that - workarounds. The need is to have some kind of encoding that is more efficient in storing the data while not letting go of the semantics. This would serve to reinforce the use of the canonical format.&lt;/p&gt;&lt;/div&gt;    </content>
  </entry>
  <entry>
    <title> How to improve ROI with SOA?</title>
    <link href="http://www.icmembers.org/blog/zaki/2007/9/18/how-to-improve-roi-with-soa" rel="alternate"/>
    <id>http://www.icmembers.org/blog/zaki/2007/9/18/how-to-improve-roi-with-soa</id>
    <updated>2007-09-18T20:15:38Z</updated>
    <author>
      <name>Danesh Zaki</name>
    </author>
    <content type="html">
&lt;div&gt;&lt;div /&gt;
&lt;div&gt;&lt;span style="font-size: 100%"&gt;Does SOA make a lot of difference to the ROI&amp;nbsp;for an environment with a good EAI setup already in place?&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;span style="font-size: 100%"&gt;I was talking to a colleague of mine on using SOA in integration projects, when she cut through the chaff and asked me if we &lt;/span&gt;&lt;span style="font-size: 100%"&gt;could show a better ROI (Return on Investment) when a project is done using SOA versus doing it &amp;quot;traditionally&amp;quot;. Traditional means could be either &lt;/span&gt;&lt;span style="font-size: 100%"&gt;by custom programming or buying commercial integration components/products, which would essentially be plain EAI. Most of &lt;/span&gt;&lt;span style="font-size: 100%"&gt;the organizations are aware of EAI products and are engaged in doing integration using them in some form or the other, which leads us to the following&lt;/span&gt;&lt;span style="font-size: 100%"&gt; questions:&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;
&lt;ol&gt;
    &lt;li&gt;&lt;span style="font-size: 100%"&gt;Can doing an integration project with SOA get a &lt;span style="font-weight: bold"&gt;significantly &lt;/span&gt;better ROI vs. doing it with EAI products?&lt;/span&gt;&lt;/li&gt;
    &lt;li&gt;&lt;span style="font-size: 100%"&gt;In either case, do we need to optimize our business processes too to see a better ROI?&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;
&lt;p&gt;&lt;span style="font-size: 100%"&gt;Any thoughts are welcome.&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;    </content>
  </entry>
</feed>
