Issue link: https://epubs.iltanet.org/i/50188
ADVANTAGES OF STAYING ON THE GROUND The reason these surprises crop up is that the experience firms have working with traditional software products don't necessarily carry over. When systems are onsite, IT has more integration options. If an application vendor provides an insufficient API, or no API at all, most organizations have database administrators and developers who can build scripts using tools like Microsoft Data Transformation Services (DTS) or SQL Server Integration Services (SSIS) to move the information in and out of the system. And, of course, firms that use a dedicated integration platform have additional advantages and expectations, including faster project execution, leveraging prebuilt templates and code-free connectors, and automated error-checking, logging and alerts. CAN WE CONNECT WITH THE CLOUD? The cloud poses problems because firms are much more dependent on the native access capabilities offered by remote systems. Unlike locally managed software, there are fewer "workarounds." For example, an enterprise-grade cloud application should provide an object-oriented Web service API accessible via either SOAP or Representational State Transfer (REST); but some might only support basic flat-file import/export for data movement, a serious warning flag. Furthermore, even if a cloud system offers a modern API, before signing up as a customer, firms should carefully evaluate how broad and deep its methods are (native functions and capabilities). Consider how you need to integrate the system into your environment and map the business processes and 22 Tech Potpourri ILTA White Paper information you need to move to and from the system — both today and in the future. Areas you should understand about the cloud system and API include: • What the API will and won't let you do • What level of real-time access to data the system will provide, if any • How the software handles updates • To which data elements the software's API restricts customer access (through means such as encryption, binary storage or other proprietary barriers) • If the system supports industry master data management standards and practices • The vendor's API roadmap and how it maps to your long-term needs and objectives BUILDING BRIDGES As previously discussed, most firms have in-house technical staff with some level of traditional integration skills. And there are two basic approaches you can take to connecting cloud-based services with the processes and products that live on the ground. The first is custom development, leveraging in-house resources or consultants. If you're planning to travel this path, make sure that your teams (and partners) are up to speed with the latest technical knowledge they'll need to be effective and efficient. There are several buzzword-compliant areas to navigate for Web service success, including: SOAP, XML, HTTP, REST and ODATA, along with several