Ads by TechWords

See your link here
Receive the latest technology news and information.
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
Cloud Computing
View all newsletters




Privacy Policy
 

SaaS integration: Tricky, but manageable

One-off integrations lead to trouble as SaaS use multiplies. But IT will get help this time.

March 23, 2009 12:00 PM ET

Computerworld - It was almost too much of a good thing. When Hines Interests Ltd. launched its real estate investment trust business, Hines Real Estate Securities Inc., as a complement to its real estate development business, it built the IT infrastructure around a bevy of SaaS products. But the need to exchange data between various hosted applications -- transaction processing, CRM, literature-fulfillment, and expense and vendor payment systems -- created a tangled web of integrations linking SaaS to SaaS and SaaS to on-premises applications.

It's the SaaS twist: Add too many applications, and you might to find yourself back in the bad old days, when the various applications in the corporate infrastructure wouldn't talk to one another. "When you're heavily reliant on SaaS, you're putting yourself in the position of siloed data once again," says Benny Lasiter, business systems architect at Hines Real Estate Securities.

At least Lasiter had a plan. In many organizations, SaaS offerings sneak in through the departments within individual business units, often without the knowledge of IT. Rogue projects have become "the profile of SaaS" in the enterprise, says Ron Papas, senior vice president and general manager of Informatica Corp.'s on-demand group.

Later, as those applications multiply and grow, problems arise. "You do it once, twice, and five times later, you have these disparate solutions coming into the IT infrastructure. There's no strategy, no consistency, and there's a problem," says Benoit Lheureux, an analyst at Gartner Inc. "Most companies don't even know that they should have a SaaS integration strategy, let alone align that with their internal B2B integration strategy. That is a huge problem."

But you need not go it alone. As IT executives are working through their SaaS tangles, they're developing fresh integration strategies and getting help from new tools and integration specialists.

Three ways integrations can get tangled up

Things can go wrong even after SaaS applications are integrated with the rest of your infrastructure. Pervasive Software says these are three of the most common challenges:

1. New features that raise the bar: The SaaS vendor adds new features that you would like to use. Example: The vendor offers more granular reporting, but the process flows you've built need to change to take advantage of that.

2. "Improvements" to the SaaS vendor's API: SaaS vendors may revise application programming interfaces several times per year, and that can cause problems with customized integration work. Example: Outbound messaging is a mechanism that notifies another application that a change to the data has occurred and that an update may be needed on the other end. "For various reasons, SaaS vendors have had to change how that signal appears to the outside world," says David Inbar, director of marketing at Pervasive Software. That forces changes that may appear to be small details but still require altering your integration process or mapping.

Salesforce.com Inc. strives to ensure that updates don't break the way its API processes transactions. "Where that may fall down is if we change the behavior of the API calls. If it behaves differently, the customer's integration code may not know what to do," says Ariel Kelman, senior director of product marketing at Salesforce.com. To avoid such problems, the company keeps old API versions online.

3. Self-inflicted wounds: You make changes to your business processes that break the system. Example: You build a system for purchase orders and then decide to split the workflow for small and large customers, changing the process and information flows through one or more SaaS or in-house applications.



Jump to comments

software as a service

Additional Resources

Microsoft
Here are some of the key reasons why you would want to run Unified Access Gateway with DirectAccess.
Microsoft
Review how one energy firm tightened protection and simplified IT work using business-ready security solutions.
Sybase
In this white paper, IDC analyzes the role of next-generation mobile enterprise platforms as organizations seek a more strategic deployment of mobile solutions.

Learn the important issues you must consider before starting your next mobility initiative. Get your mobility white paper from IDC now, compliments of Sybase.

What People Are Saying

Featured Zone
Strategic Content Management
Learn how the right Enterprise Content Management (ECM) solution can start saving you money within a week and pay for itself in as little as three months. These case studies and white papers provide practical information on how to go from theory to reality - to help you put together a plan that will achieve your content management and process automation goals.
Enter the Strategic Content Management Zone now


IT Jobs