The Evolution of B2B in a Web Services World
By Paul Lipton, Computer Associates
Reprinted from IT Solutions Guide, Spring 2004 issue, with permission of SYS-CON Media (http://www.sys-con.com/it)
The use of Web services as a simple means of enabling two companies to do business together in an automated fashion is now common. Web services can provide a low cost path to distributed application interoperability. Often, that's all that’s required by IT organizations when short-term problems or opportunities arise. However, enterprises with more clearly articulated long-term goals are beginning to recognize the value of using Web services as the foundation for building a Service-Oriented Architecture (SOA).
Today, many IT leaders agree that a SOA is an essential approach to solving the many challenges facing them today. At an abstract level, many of these challenges could be expressed as the need for IT to contribute more to the business at a time of increasing change and globalization. In short, the mandate is to move IT from being cost center to being a revenue and opportunity center. SOAs enable the necessary alignment between business goals and technology by making automated business processes more valuable and dynamic – able to adjust to changing business conditions and to collaborate with trusted partners and suppliers, customers, and regulatory agencies.
Service-Oriented Architectures will increase the value of automated business processes by extending them beyond organizational borders as Web services. Given cost and time-to-market constraints, many organizations will choose to concentrate their efforts on services that contribute to core business functions while outsourcing the less critical or more obscure functions. To use a simple example, a chain of restaurants might develop its own services to control mission-critical food orders from partner's Web services (an important part of the restaurant business). But, they may utilize an outside geographic Web service such as that provided by Microsoft’s MapPoint in order to provide good driving directions on their website since geographic expertise is not likely to be a core competency in their IT organization.
How can IT insure that the intricate mesh of Web services supporting a Service-Oriented Architecture will work well? You cannot build a robust Service-Oriented Architecture on a foundation of unmanaged Web services. Any architecture – from mainframe to client-server to n-tier to Service-Oriented – requires visibility and control into the key processes and entities that constitute that environment. For Service-Oriented Architectures this need for visibility and control occurs at two distinct levels: the infrastructure level and the message level.
For any Web service hosted within an enterprise, it is unquestionably important for the IT operations staff to have an understanding of the underlying infrastructure that supports that Web service. At the heart of every Web service is the business logic that it encapsulates. That business logic is in turn supported by a wide range of hardware (routers, network cards, hard drives, etc.) and software (web servers, application servers, databases, byte-code virtual machines, etc.) that must all function properly for the Web service to work. Thus, in order to identify the underlying cause of Web service disruptions (perform true root-cause analysis) as well as to measure and control how infrastructure hardware and software affect the Web service, traditional enterprise management of the underlying infrastructure continues to be an absolute necessity.
But, because Web services are primarily about an entirely new technology layer and the business messages that are exchanged at that layer rather than underlying infrastructure and business logic, per se, new types of Web services management solutions must also be made available. This new generation of Web services specific management software must function at a logical level above traditional IT infrastructure management, and yet must still be deeply integrated with existing infrastructure management so that both levels of management can correlate and share information about their corresponding responsibilities in the SOA.
Integration between these two distinct levels of SOA management, infrastructure and Web services, will make it easier for a company to build a reliable and scaleable SOA. In my opinion, CA has been very sensitive to this. We designed our new Web services management solution, Unicenter WSDM (Web Services Distributed Management), with the SOA in mind. While it can be deployed in a standalone fashion suitable for more narrowly focused Web service deployments, it can also be deployed with our enterprise infrastructure management solutions providing integrated support for both levels of the SOA. Other leading management and security vendors are likely to follow suit with similar approaches.
In the meantime, the best approach to developing automated business processes that span multiple domains continues to be to a policy that emphasizes incremental deployment of secure and manageable Web services to address short-term tactical issues while staying fixed on the long-term goal of a comprehensive SOA. Web service deployments that lack manageability are unlikely to address any goals.
Reprinted from IT Solutions Guide, Spring 2004 issue, with permission of SYS-CON Media (http://www.sys-con.com/it)
|
