Service-Oriented Architecture Consulting for Enterprise End-Users

Service-Oriented Architectures (SOAs) represent an evolutionary approach to distributed computing that promises a flexible IT environment that leads to business agility. As companies look to leverage the business advantages of Web Services to address strategic business needs, they are increasingly looking to build SOAs. However, SOAs require special skills and expertise. When companies do not have such skills in-house, they turn to consultants, system integrators, and other professional services organizations.

The movement to SOAs present both opportunities and threats to consulting firms: on the one hand, there will be an increased demand for architectural consulting, business process consulting and the implementation tasks associated with building SOAs. On the other hand, as SOAs take hold and Service-oriented process solutions supplant integration solutions, the market for system integration will dry up, requiring system integrators to change their business focus.

This report analyzes the market for SO

Service-Oriented Architecture Consulting Partnership Landscape

Service-Oriented Architectures (SOAs) represent an evolutionary approach to distributed computing that promises a flexible IT environment that leads to business agility. As companies look to leverage the business advantages of Web Services to address strategic business needs, they are increasingly looking to build SOAs. However, SOAs require special skills and expertise. When companies do not have such skills in-house, they turn to consultants, system integrators, and other professional services organizations.

The movement to SOAs present both opportunities and threats to consulting firms: on the one hand, there will be an increased demand for architectural consulting, business process consulting and the implementation tasks associated with building SOAs. On the other hand, as SOAs take hold and Service-oriented process solutions supplant integration solutions, the market for system integration will dry up, requiring system integrators to change their business focus.

This report analyzes the market for SO

Service-Oriented Process

Business processes have always been an important, if understated, asset of enterprises. The nature and methods by which a company runs its business changes on a daily basis at various different levels in the company — from high-level strategic changes to lower-level implementation details. As a result of these changes, enterprises constantly struggle to make their businesses more responsive to business changes by connecting their business requirements to their IT and human capabilities.

However, automating business processes has historically been a difficult-to-achieve goal for most enterprises due to the flexibility of their IT infrastructure. Fortunately, businesses have a solution in Service-Oriented Process: a separate abstraction layer for business process definition and execution that leverages the capabilities of Service-oriented Architectures. Service-Oriented Process provides businesses an approach to tying business requirements to the Service model represented in the SOA metamodel, thereby providing a flexible approach towards implementing architectures that promote business agility.

SOA Best Practices

From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best pra

SOA Tools

From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best pra

SOA Tools and Best Practices

From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best practices as well as an analysis of the tools that are currently available for building Service-oriented architectures.

XML in the Content Lifecycle

The process of creating content — information meant for human consumption — is almost always extremely effort-intensive. People must spend time organizing information prior to creation, constructing the content, and laying out the information so that it is easily read. With so much time, cost, and effort invested in content, it makes sense to reduce costs by reusing content as much as possible. Furthermore, content-oriented processes involve a complex set of interactions that progress in a “Content Lifecycle” consisting of five major stages: content creation, management, publishing, syndication, and protection. Each of these phases requires different technologies, processes, and resources.

By rearchitecting content representation technologies to treat content as another asset in the corporate IT infrastructure, businesses can realize the benefits long promised to us by reusable and agile content. But first, we need to move from ad-hoc content creation to content componentization, and then to content services. XML and Web Services are the key to this transition that can help organizations maximize the value of their content.

XML Data Store Multi-Client Study

While much has been written about XML data storage, none of the research to date has focused on the key questions:

• What are the different needs for XML data storage?
• ow do those needs translate into different storage requirements?
• How are various vendor solutions best suited to meet these different needs?

In attempting to understand the answers to the above questions, ZapThink realized that there was no single answer for any of these key questions. In fact, it seems that the various requirements for XML data storage pull end-user customers in different directions when they are deciding how to implement XML storage requirements. As such, this study seeks to do what no other study before it has done: show that XML data storage is not a distinct market segment, but instead a functionality requirement for applications that require XML storage in order to achieve their overall system objectives.

Service-Oriented Management

Web Services management applications provide software that helps companies manage the systems and applications that underlie their Web Services implementations. The Web Services management products on the market today offer functionality in five basic categories: system management, lifecycle management, business management, security management, and the most important, Service-Oriented Architecture enablement.

The latter category is especially important because many Web Services management products provide the critical infrastructure necessary for companies to take their fine-grained, atomic Web Services and other data sources and encapsulate and compose them into coarse-grained business Services that make up a Service-Oriented Architecture. Such architectures offer far more long-term business value than the point-to-point applications of Web Services common today.

Service-Oriented Management Technology Landscape

Web Services management applications provide software that helps companies manage the systems and applications that underlie their Web Services implementations. The Web Services management products on the market today offer functionality in five basic categories: system management, lifecycle management, business management, security management, and the most important, Service-Oriented Architecture enablement.

The latter category is especially important because many Web Services management products provide the critical infrastructure necessary for companies to take their fine-grained, atomic Web Services and other data sources and encapsulate and compose them into coarse-grained business Services that make up a Service-Oriented Architecture. Such architectures offer far more long-term business value than the point-to-point applications of Web Services common today.