Presentation-Layer Web Services

Download File

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.

Eleven Years of Productivity

Jason Bloomberg, an analyst with ZapThink LLC, of Cambridge, Massachusetts, has noticed 9.0’s versatility. “PowerBuilder 9 is an XML development tool as well as a Web Services development tool.”

Read more at: Sybase Newsletter

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

ZapNote: Sybase

Download File

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.

Service-Oriented Integration

Connecting systems both within the enterprise and with suppliers, partners, and customers is of critical importance to today’s enterprise. However, integration remains complex, expensive, and risky. While Web Services won’t be the magic bullet that immediately solves these problems, they enable a new approach to integration. Service-Oriented Integration (SOI) leverages open standards, loose coupling, and dynamic description and discovery capabilities of Web Services to reduce the complexity, cost, and risk of integration. This report identifies the key aspects of SOI, solutions for implementing SOI, ROI metrics, and critical challenges.

2002 Retrospective and Thinking Ahead

Maybe it’s the end of the year that brings retrospective thought, or perhaps it’s one too many post-holiday feast chats over eggnog, but in any case, it is the habit of many an analyst and journalist to think through all the events of the previous year and guess how the …

ZapThink: Big changes ahead in XML data storage

The beginning of 2003 marks ”the end of the Native XML Data [NXD] store market as we know it,” proclaimed Ronald Schmelzer, senior analyst at ZapThink, LLC, a Waltham, Mass.-based analyst firm specializing in XML.

This does not mean that NXD vendors will disappear, although larger software companies may acquire some of the smaller ones; but the way XML data storage products are marketed and deployed will change, he said.

Read more at: Application Development Trends