IBM Buys Web Services Pioneer Bowstreet Inc.

In fact, Bowstreet and IBM share over 100 joint customers, and the partnership was so close that IBM’s own software group would sell Bowstreet’s product. ” Bowstreet has essentially become a WebSphere Portal portlet vendor, so they were already well within IBM’s orbit,” according to Jason Bloomberg, a senior analyst with Web services consulting firm ZapThink LLC. The WebSphere Portal is IBM’s package of software development tools that help programmers create intranet sites and Web sites that integrate different types of applications.

“The challenge Bowstreet had with selling themselves was that there were so many investors in Bowstreet over the years, with so much dilution, that I’m sure nobody stood to make much money on this deal,” Bloomberg said.

Read more at: CNN Money

WS-I Readies Web Services for Supply Chains

ZapThink Senior Analyst Jason Bloomberg said the delivery of the sample applications will free WS-I up to conduct other interoperability tests.

“Now that these deliverables are off the WS-I’s plate, they can focus more specifically on building the interoperability profile for Web Services security — a tougher problem than basic interoperability, but every bit as important,” Bloomberg told internetnews.com.

Read more at: InternetNews.com

Startup Writes Language to Replace Java, .NET

ZapThink.com [sic] Senior Analyst Jason Bloomberg said Clear Methods’ approach is an interesting one, albeit a challenge in a market where so many niche players are trying to develop Web services products that aim to complement or compete with software one of the giant vendors, such as Microsoft or IBM, don’t have.

“Programmers can do object-oriented programming, middle tier programming, and presentation-layer programming, all with the same language, and it’s all XML,” Bloomberg said. “They have a solid approach to security and as you would expect, Web Services are a no-brainer.”

ZapThink Senior Analyst Ronald Schmelzer agreed there are ways in which large companies can’t take advantage of XML as small companies can, “and I think that’s the story here. But that’s the typical story for startups — there’s always opportunity to do things in a way that large vendors can’t due to their size and flexibility.”

Read more at: Internetnews.com

ISEs Give Developers a Helping Hand

“WebPutty’s key strength is that they offer the tools to provide a level of abstraction above each of the tiers in an n-tier architecture,” said Jason Bloomberg, an analyst with ZapThink LLC, a Cambridge, Mass., market research firm. “In other words, a WebPutty developer is working on the presentation tier, middle tier and data tier all at once, in the same tool, without having to jump back and forth. The WebPutty Application Platform handles all the plumbing issues behind the scenes–maintaining consistency, preserving scalability, etc. Furthermore, WebPutty does it all with XML metadata–which means that the entire service-oriented architecture can be moved from one set of servers and applications to another without any recoding.”

Read more at: eWeek

Overview of Web Services Management

Download File

Overview of Web Services Security

Download File

ZapNote: Bowstreet

Download File

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 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.

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