 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SaaS integration easier said than done</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/total-cio/saas-integration-easier-said-than-done/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/total-cio/saas-integration-easier-said-than-done/</link>
	<description>A SearchCIO.com blog</description>
	<lastBuildDate>Sat, 11 May 2013 17:51:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Mark Silber</title>
		<link>http://itknowledgeexchange.techtarget.com/total-cio/saas-integration-easier-said-than-done/#comment-402</link>
		<dc:creator>Mark Silber</dc:creator>
		<pubDate>Mon, 01 Dec 2008 16:25:23 +0000</pubDate>
		<guid isPermaLink="false">http://totalcio.blogs.techtarget.com/1969/12/31/saas-integration-easier-said-than-done/#comment-402</guid>
		<description><![CDATA[As an IT system architect for a large company, I have extensive experience with Salesforce.com and integration. Although it&#039;s &quot;in the cloud&quot;, it doesn&#039;t necessarily mean integration will be more difficult than with an on-premise application since a lot depends on your integration strategy. For example, if your integrations are primarily at the database level using direct database connections (i.e., PL/SQL), then integration will be difficult without an integration tool that sits between Salesforce and your database (CastIron, Relational Junction, etc.). However, if your integrations are more modern SOAP / web services or TIBCO, then integration to Salesforce will in most cases be easier due to the very open and robust API Salesforce provides. There have been a lot of misconceptions about integrating with Salesforce versus an on-premise application like Siebel. My experience over the last few years has shown integrations are actually easier -- not harder with Salesforce than our previous on-premise CRM system.]]></description>
		<content:encoded><![CDATA[<p>As an IT system architect for a large company, I have extensive experience with Salesforce.com and integration. Although it&#8217;s &#8220;in the cloud&#8221;, it doesn&#8217;t necessarily mean integration will be more difficult than with an on-premise application since a lot depends on your integration strategy. For example, if your integrations are primarily at the database level using direct database connections (i.e., PL/SQL), then integration will be difficult without an integration tool that sits between Salesforce and your database (CastIron, Relational Junction, etc.). However, if your integrations are more modern SOAP / web services or TIBCO, then integration to Salesforce will in most cases be easier due to the very open and robust API Salesforce provides. There have been a lot of misconceptions about integrating with Salesforce versus an on-premise application like Siebel. My experience over the last few years has shown integrations are actually easier &#8212; not harder with Salesforce than our previous on-premise CRM system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Roehm</title>
		<link>http://itknowledgeexchange.techtarget.com/total-cio/saas-integration-easier-said-than-done/#comment-401</link>
		<dc:creator>Steve Roehm</dc:creator>
		<pubDate>Sat, 29 Nov 2008 02:29:07 +0000</pubDate>
		<guid isPermaLink="false">http://totalcio.blogs.techtarget.com/1969/12/31/saas-integration-easier-said-than-done/#comment-401</guid>
		<description><![CDATA[As an ex-CIO, I can understand that all of us have made mistakes on migrations (and unfortunately will probably continue to do so), but your description of the issues makes me think that the &quot;buyers&quot; needed to ask more questions (remember the age old phrase - &quot;buyer beware&quot;) about integration and adjust accordingly based on the answers (or non-answers) they received....Migration to new software is always challenging, but stating that process changes are the biggest challenge, or that the teams should have done a sample data move unfortunately makes me think that the CIO&#039;s adopting SaaS should have done a bit more homework. That said, I am not giving the vendors (Salesforce, OpenAir, or Seibel) a &quot;pass&quot; -- they clearly could have been more helpful, but I learned early on as a CIO that you take nothing for granted, ask way more questions than would seem normal, and then still plan for a VERY challenging migration with contingency built in.....I hope all goes well for these panelists as SaaS does hold great current and future potential for all involved.]]></description>
		<content:encoded><![CDATA[<p>As an ex-CIO, I can understand that all of us have made mistakes on migrations (and unfortunately will probably continue to do so), but your description of the issues makes me think that the &#8220;buyers&#8221; needed to ask more questions (remember the age old phrase &#8211; &#8220;buyer beware&#8221;) about integration and adjust accordingly based on the answers (or non-answers) they received&#8230;.Migration to new software is always challenging, but stating that process changes are the biggest challenge, or that the teams should have done a sample data move unfortunately makes me think that the CIO&#8217;s adopting SaaS should have done a bit more homework. That said, I am not giving the vendors (Salesforce, OpenAir, or Seibel) a &#8220;pass&#8221; &#8212; they clearly could have been more helpful, but I learned early on as a CIO that you take nothing for granted, ask way more questions than would seem normal, and then still plan for a VERY challenging migration with contingency built in&#8230;..I hope all goes well for these panelists as SaaS does hold great current and future potential for all involved.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
