Intalio

Overview of Web Services Management

By Jason Bloomberg ⋅ April 17, 2003 ⋅ Post a comment

Download File

Service-Oriented Process to Cannibalize Integrators

By admin ⋅ April 17, 2003 ⋅ Post a comment

As Web services support for business processes matures, companies may be able to throw out expensive and complicated integration systems through a “Service-Oriented Process” approach, according to a new report by XML research firm ZapThink.
“A process is a set of activities that are linked together into a logical flow that meets business requirements,” Ronald Schmelzer, ZapThink co-founder and senior analyst, told internetnews.com.

Service-Oriented Process

By Ronald Schmelzer ⋅ April 16, 2003 ⋅ Post a comment

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.

New Spec Surfaces for Orchestrating Web Services

By admin ⋅ April 16, 2003 ⋅ Post a comment

“The submission of BPEL to OASIS is a great step for BPEL as well as Web services in general,” said Ronald Schmelzer, an analyst with ZapThink LLC, a Cambridge, Mass., market research firm. “BPEL is a key specification aimed at providing a mechanism by which Web services can be orchestrated into business processes, which can then be exchanged and choreographed with external processes. Business process is a critical aspect of adoption of Web services and especially service-oriented architectures since business processes are how companies define their business requirements that must then be implemented with Web services. Without process, all you have is a jumble of Web services. Specifications like BPEL bring order to the chaos by specifying a logical flow by which Web services can be orchestrated to meet defined business requirements.”

ZapNote: Intalio

By Ronald Schmelzer ⋅ April 14, 2003 ⋅ Post a comment

Download File

All Aboard for Commerce One’s Conductor

By admin ⋅ March 24, 2003 ⋅ Post a comment

ZapThink Senior Analyst Jason Bloomberg, who spoke with Commerce One recently, said he got the idea Commerce One is betting the company on Conductor.

“The company has been through too many ups and downs and has been in the red for too long,” Bloomberg told internetnews.com. “That being said, Conductor looks like a strong, comprehensive offering in the Service Orientation space. Commmerce One’s strengths in the CPG, retail, automotive, and discrete manufacturing verticals gives them a great niche to build out their offering, as many other vendors are focusing on financial services, government, and healthcare.”

ZapThink Senior Analyst Ronald Schmelzer said Commerce One is entering new ground, one fraught with heavy competition.

SOA Best Practices

By Jason Bloomberg ⋅ February 20, 2003 ⋅ Post a comment

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

By Jason Bloomberg ⋅ February 20, 2003 ⋅ One comment

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.

SOA Tools

By Jason Bloomberg ⋅ February 20, 2003 ⋅ Post a comment

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

Dancing around Web services

By admin ⋅ January 17, 2003 ⋅ Post a comment

By that, the W3C means a decision to drop intellectual property claims on the specification–which analysts don’t necessarily expect the BPEL4WS co-authors to do.

“I think the W3C should be careful, because the OASIS group could make the claim that the whole notion of Web services flow and choreography is in their purview,” said Ron Schmelzer, a senior analyst at ZapThink, a research firm that focuses on XML (Extensible Markup Language) and Web services.

FREE POSTERS