Service-oriented architecture (SOA) was one option for integrating applications into a single user workflow on a Windows desktop, said Ken Brande, director of information technology at Afni, Inc., but it is not the one he chose.

Microsoft has a unique corporate approach to architectural problems, often eschewing SOA terminology, and, as Brande proves, Microsoft developers can also follow the road less traveled shunning the often API-centric view of SOA held by many in the Java community.

Brande chose an approach called composite service integration (CSI) using Microsoft tools and technologies and a development platform from OpenSpan, Inc., which specializes in desktop integration. The OpenSpan Platform 3.0, supports .NET 2.0 and the Microsoft Customer Care Framework (CCF) 2.6.

What is unique about CSI with this technology, Brande explained, is that it has nothing to do with APIs or back office systems, which his customers did not want him to touch even while integrating their applications.

IT shop looks past SOA to Windows desktop integration - SearchWebServices.com

This entry was posted on Monday, May 7th, 2007 at 12:06 pm and is filed under Interoperability, Applications. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.