Moving to SaaS? Five Considerations for Your Application Integration Strategy
The first few years of this decade have seen consumers develop an unprecedented level of interest in the power of connecting devices. For instance, the integration on a smartphone can be mind-boggling. Your phone, camera, email, contacts, calendar, Internet searches, mapping software and even social networks and restaurant review applications are all connected. Integration is seamless, personal and transparent.
So, how does this experience translate to enterprise data systems that span the globe with data sets in the petabytes? It’s easy to integrate apps and have them tied into a network, but enterprises must manage the ever-increasing volume of data generated by this vast level of integration.
IT departments face challenges integrating the organization’s growing number of cloud-based services with the enterprise’s internal systems. They must do this in a way that meets business priorities and provides high-quality services for the user, while respecting governance and data security policies. They need a corporate-wide integration strategy to get the most out of current SaaS offerings and also have the flexibility to shift those offerings and priorities as new opportunities arise. This approach can make integration easier and help lay the groundwork for your organization’s future in the cloud.
Where Do You Begin?
With SaaS, you are integrating an external service, hosted by an external party, with your internal systems. The SaaS integration involves connecting the clouds and well-articulated interfaces, along with defining the data that is traveling back and forth. With the right integration strategy, SaaS integration can be simple, straightforward and easy. It can position your IT organization to effectively leverage SaaS and migrate from one SaaS solution to another to avoid vendor lock-in. Here’s a word of caution: Avoid locking yourself into a SaaS contract for more than 24 months because you may wind up with technology that is outdated.
Be sure to consider these factors when developing your integration strategy.
1. Determine the People and Processes Required
Identify the “people and processes” portion of the equation. You need to understand how processes are orchestrated and defined inside of the SaaS solution and inside of your business as a whole. Then think about how the data moves — the data definitions. Ask yourself, “How is the data represented in each system along the way? How do systems communicate with each other?” Because SaaS is based on more agile technologies than on-premise solutions, the “plumbing” portion of the equation is generally taken care of for you, typically in the form of Web services.
2. Understand How you are Processing and Integrating Data
You must know what you have in the infrastructure. The main cost of integration isn’t just about connecting into the SaaS provider, it is also about exposing your existing systems. If you already have the key services you require (along with the service bus) and you have defined the services, then integration with SaaS can happen very quickly. With SaaS, it’s really mostly a matter of how fast you can get the businesspeople to agree upon the processes and the deployment date, and less about coding and deployment itself.
Data definitions and representations will often differ between systems. Data management is challenging, and without a common data model and logical mappings integration becomes unwieldy.
3. Know how SaaS Facilitates Efficient Delivery
Service delivery is really about focusing on the software and the service. Many parts of the stack are being handled for you by the vendor. One of the ways the vendor does that is by abstracting data services, as well as other applications and services that you link into, so you no longer have to focus on those services.
It’s almost like imagining an integration project where one side of the integration is already very well-defined, using the latest and greatest standards. At that point, all you have to worry about is whether the customer’s infrastructure operates like yours. If so, the primary concern is to identify what objects you are passing back and forth between the two systems.
The process for identifying what objects are passed back and forth is easy to define. Plan to spend more time with your management team and business analysts discussing which objects are shared and how a process works than you do on writing the software. This approach helps increase efficiency with SaaS integration. Some businesses have been able to complete major integrations in less than two weeks, rather than many months, because all they had to worry about was how the data was moving back and forth.
From an agility standpoint, these abstracted data models can be changed very easily without rewriting the entire integration. As a result, you can start off with a simple integration where you’re merely passing an object from one place to another. Then, using an agile model, you can release that capability to your end users and improve it over time. Since you need to do a full rewrite every time you make changes — and, of course, the SaaS vendors allow for this model — you should be able to iterate and deliver integrated capabilities in a much faster, more agile way with SaaS.
4. Tackle the Most Important Challenges
With IT service management integration, you can expect to encounter the same integration challenges as you did with on-premise initiatives. With SaaS and on-premise models, you must deal with data definitions and processes. In the on-premise world, if some of the software is older, it may not have sufficiently defined interfaces. This creates challenges in terms of development and maintenance. Therefore, in the on-premise world, you would expect to do more of the heavy lifting yourself because you need to — in some cases, coding all the way down into challenging application programming interfaces. With SaaS, however, the providers should offer a well-defined set of APIs, instead of interfaces, and a well-defined data dictionary.
However, in the cloud, the challenge changes. Outbound communications are straightforward because you are initiating the connection from outside of the enterprise into the SaaS solution. This can be achieved by setting up an https site for this connection to occur.
In the case of inbound communications from the SaaS solution calling into your enterprise, you basically have two choices: You can either create a polling service that is called out periodically to the SaaS solution, or you can call into the enterprise from the SaaS solution, leveraging the client-side certification for authentication.
Of course, you need to be concerned about security, as you are pushing data in and out of the enterprise into the SaaS solution. That’s why it’s important to determine whether you are comfortable opening up a firewall so that the SaaS provider can call directly into your enterprise. To address this concern, keep in mind that the firewall will accept requests only from a certain provider and a certain IP range and you can use a cloud certification capability to handle the authentication portion. Essentially, this allows you to open up only a portion of the firewall to the SaaS provider.
Another option is to set up a virtual private network connection between the SaaS provider and your own infrastructure. That makes the SaaS providers look like they are a part of your network, making the user experience easier. However, with a VPN solution, you need to factor in the cost of maintaining a virtual private server.
5. Use a Corporate-wide Integration Strategy
A corporate-wide integration strategy and support for integration should be built into your ITSM solution. If you don’t have a good integration strategy and are not sure how integration is supported by the solution, the end result will be a lot of point-to-point, one-off implementations and one-off integrations. Over time, these one-offs begin to look like tangled spaghetti. That haphazard approach to integration is difficult to maintain and update — and can cause you to lose some of the agility, efficiencies and integration aspects of a SaaS solution.
Cloud computing makes an enterprise-wide service integration strategy more important than ever. Before the growth of SaaS, the need for an integration strategy was something that CIOs could put on the back burner, but the advent of cloud brings it to the forefront. As helpful as having both the enterprise service and the integration strategy can be, these can often be put on hold because of the challenge of obtaining funding. However, a focus on business priorities is important. CIOs and architects must make the case for an integration strategy by aligning it with business initiatives.
One way to achieve this objective is by pointing out to your stakeholders that developing an integration strategy helps to lay the groundwork for the cloud. IT organizations must focus not only on which SaaS provider to use, but also on the bigger picture of whether the organization is cloud-ready. Having a comprehensive integration strategy is one of the critical ways that you can make that happen. ITIL best practices suggest involving the business relationship manager and the Service Management Office to focus on the cultural readiness of the organization.
It’s important to be aware of the exponential nature of technological changes. The first three years of this decade will be much different than the next seven. Future systems will not resemble many of the frameworks that we have today. Systems based on large data sets from mobile apps will introduce new complexities to integrators in the second half of the decade.
SaaS integration is fundamental for supporting your business’s operations in the cloud — both now and in the future. With the right strategy, achieving integration can be simple and straightforward. Treat your own organization like a SaaS solution. Just as SaaS vendors have clean data and service-oriented APIs available, think about your own services and IT in a similar way. This will help you set up your IT organization for success down the road by leveraging SaaS and being able to migrate away from one SaaS solution to another. Having these strategies in place can help you to avoid vendor lock-in, while growing the services you provide to the business.