Archive for the ‘SOA’ Tag

ESB Interoperability Standards

Thousands of Enterprises worldwide have adopted the principles of Service Oriented Architecture (SOA). SOA provides an architectural approach that brings the flexibility and agility required by today’s global business environment. An Enterprise Service Bus (ESB) is a vital ingredient of SOA that facilitates the interaction of business services by mediating the message exchanges between them.

ESB infrastructure products are available from a number of software vendors, but there is a lack of consistency between them when it comes to standards support. This has led a number of ESB customers to ask for an industry-wide agreed list of standards supported by an ESB. This Whitepaper documents the essential standards requirements for an ESB, using a scenario-based approach.

ESBs extend the capabilities of SOA and advance the realization of SOA. Mediations can be employed to facilitate interactions between mismatched service requesters and providers. The ESB also provides a common model for accessing, managing and administering system-wide services.

Today’s fast-paced business world demands the ability to change and adapt rapidly. With an Enterprise Service Bus, you can connect your business applications and processes quickly and easily as you respond to business challenges and opportunities when they arise.

By adopting a standards-based approach leveraging Web services a customer has the assurance of the flexibility and the interoperability that such a strategy provides.

Read the full Whitepaper by Thomas Freund and Peter Niblett here:


Nearly half of UK companies go for SOA

The SOA readiness survey of 180 UK organisations by Birmingham-based systems integrator Griffiths Waite showed that of the 47% of respondents pursuing SOA, 20% had already implemented at least one SOA project.And of that 20%, almost half (49%) said their main reason for adopting SOA was to achieve IT flexibility and 14% said it would enable them to get the most out of their IT investments by providing industry standards for accessing functionality and resources.

Hugh Griffiths, director of Griffiths Waite, said, “This shows UK companies are starting to put money behind SOA, which represents a definite shift away from technical discussions towards mainstream implementation.”

Griffiths said another reason for the shift was an increase in the number and maturity of standards, such as the Business Process Execution Language (BPEL) for specifying business process behaviour for web services.

Read the complete article in Computer Weekly

“Next Generation Grid Enabled SOA”, video replay

An interesting video recording of a SOA Grid presentation by David A. Chappell at the BeJUG Enterprise SOA Conference has just become available at:

Topics include :

– A new grid based service bus infrastructure concept that combines process flow, horizontally scalable service state caching, and ESB mediation.
– Fault tolerant in memory data grid
– A controversial subject that I call “Not Your MOM’Bus”
– Patterns for transparent state management of load balanced services
– Patterns for transparent fault tolerance of stateful services
– Optimal server resource allocation that is complementary to virtualization strategies.

Nexaweb Expands with HP’s SOA Governance Leadership

Nexaweb announced its membership to the HP Governance Interoperability Framework (GIF).

GIF provides a collaborative, standards-based approach for publishing, associating, accessing and managing service-oriented architecture (SOA) metadata and business service information across multiple vendors and technologies.

Nexaweb’s membership to HP GIF bridges the gap between SOA and application development, which helps to make it easier to build Web-based business applications using governed services from a central repository. Using Nexaweb’s Enterprise Web Suite, enterprise architects and developers can quickly search and retrieve artifacts and services from the HP SOA Systinet and use those services to build and deploy governed, rich Internet, composite and enterprise mashup applications.

Complete Application & SOA Governance with Nexaweb
Nexaweb’s Enterprise Web Suite is a complete application development and deployment platform for Web-based business applications.  A core component of the suite is Nexaweb Studio, an Integrated Development Environment that enables visual, drag and drop application development and maintenance.  Nexaweb Studio interoperates with the HP SOA Systinet through an RSS interface. 

Using a wizard, developers can retrieve services and place them into Nexaweb Studio’s Service Explorer.  Designed to maintain information about the service and information manager, the Service Explorer removes the need to import WSDL files directly into the workspace.  This creates a ‘loose’ coupling between the implementation and the service, making it possible to maintain a centrally-managed repository for all services. 

Full article …

2008 Predictions – SOA, Grid, SCA, Web 2.0, REST, etc.

Here are David A. Chappell’s predictions for 2008:

– Grid computing will grip the attention of enterprise IT leaders, although given the various concepts of hardware grids, compute grids, and data grids, and different approaches taken by vendors, the definition of grid will be as fuzzy as ESB. This is likely to happen at the end of 2008.

– At least one application in the area of what Gartner calls “eXtreme Transaction Processing” (XTP) will become the poster child for grid computing. (see Gartner Research ID # G00151768 – Massimo Pezzini). This “killer app” for grid computing will most likely be in the financial services industry or the travel industry. Scalable, fault tolerant, grid enabled middle tier caching will be a key component of such applications.

– Service Component Architecture (SCA) will become the new way for SOA applications to be defined as support from all the major platform vendors (sans Microsoft) will be rolled out.

– By end of year it will be clear that an understanding of infrastructure requirements for common problems such as predictable scalability, reliability, security, (*-ilities) will be necessary in order to support any combination of SOA, REST, or Web 2.0 style applications. However the exact architecture or even the list of requirements in support of such infrastructure will not be well understood or agreed upon. Such a common understanding will not come to bear until at least 2010. This will be the new frontier to explore in the coming years.


What the statistics are telling us about SOA

Here are a few highlights from past year’s studies of SOA adoption:

57% of executives expect to see cost reductions as a result of SOA, while 27% cite code reuse and 23% expect to increase business agility. (Saugatuck)

50% of new mission-critical operational applications and business processes were designed this year around SOA, a number will jump to more than 80 percent by 2010. (Gartner)

40% of companies with SOA spend between 10 and 30 percent of their overall IT budgets on SOA projects. Most have increased their SOA budgets over last year. (IBM)

48% of CIOs are planned to open their SOAs “to the cloud” in 2007 — the cloud being “where their current and potential trading partners are.” (McKinsey)

37% of companies implementing SOA report seeing positive return on investment from SOA — which, by the way, isn’t too shabby (Nucleus Research)

29% of companies with advanced SOA deployments are using SOA governance software, compared of 17% of companies still in earlier stages of SOA. (Aberdeen)

61% of advanced SOA deployers saw a reduction in the number of software defects discovered in production, compared to 18% of non-deploying companies could say they were able to reduce defects. (Aberdeen)

49% of developers working with SOA say they can now complete a typical SOA project within three months – more than twice as many as a year ago. Plus, more than 60% of all SOA projects are now developed and deployed within just six months. (Evans Data)

75% of mainframe users said they want to modernize their systems. But 52%, also said they had concerns about their system’s ability to actually support SOA. (Software AG)

25% of mainframe companies have SOA efforts now in progress, and another one-third are planning or considering SOA. At least half say they are or will employ mainframes in a central role in SOA. (Unisphere Research/SHARE)

55% of executives view SOA as “the best way to support the use of social networking and Web 2.0 development techniques in their IT infrastructure.” (BEA)

56% of executives at companies deploying SOA admit that at least half of the code or artifacts developed under their roofs are not reviewed for compliance before moving into production. (SOA Forum)

15% of small companies (with fewer than 100 employees) have SOA efforts underway, compared to 35% of companies with more than 500 employees. (Nucleus Research)

12%that’s the average growth rate of companies with “well-aligned IT-business operations,” versus 4% overall. (BTM Institute)

A Brief Introduction to REST

You may or may not be aware that there is debate going on about the “right” way to implement heterogeneous application-to-application communication: While the current mainstream clearly focuses on web services based on SOAP, WSDL and the WS-* specification universe, a small, but very vocal minority claims there’s a better way: REST, short for REpresentational State Transfer. In this article, I will try to provide a pragmatic introduction to REST and RESTful HTTP application integration without digressing into this debate. I will go into more detail while explaining those aspects that, in my experience, cause the most discussion when someone is exposed to this approach for the first time.

Key REST principles

Most introductions to REST start with the formal definition and background. I’ll defer this for a while and provide a simplified, pragmatic definition: REST is a set of principles that define how Web standards, such as HTTP and URIs, are supposed to be used (which often differs quite a bit from what many people actually do). The promise is that if you adhere to REST principles while designing your application, you will end up with a system that exploits the Web’s architecture to your benefit. In summary, the five key principles are:

  • Give every “thing” an ID
  • Link things together
  • Use standard methods
  • Resources with multiple representations
  • Communicate statelessly

Let’s take a closer look at each of these principles …

OASIS Advances Service Data Objects (SDO) Architecture

OASIS, the international open standards consortium, has formed a new technical committee to advance the Service Data Objects (SDO) specification, which is designed to simplify the way in which Service Oriented Architecture (SOA) applications handle data. Using SDO, application programmers can uniformly access and manipulate data from heterogeneous data sources, including relational databases, XML data sources, Web services, and enterprise information systems.

“Most of the data programming technologies in use today are specific to a single type of data source, but in real-world applications, data frequently comes from a variety of places. As a result, application developers are burdened by the need to learn a plethora of programming models and data access APIs,” noted Shawn Moe of IBM, convenor of the OASIS SDO Technical Committee. “By offering a common facility for representing collections of data–regardless of data source type–SDO gives application developers a more simple, unified programming model and enables tools to work across heterogeneous data sources consistently.”
more …

ebMS 3.0 and support for SOA

OASIS, the international open standards consortium, announced October 16th that its members have approved ebXML Messaging Services (ebMS) version 3.0 as an OASIS Standard.

The V3.0 specification provides a raft of new features that enable extended B2B interchanges and support for SOA message transport layer services.

ebMS V3.0 is designed to be used either with or without any of the other ebXML standards.

V3.0 now includes capability to use WS-Security, WS-Reliability, and the WS-ReliableMessaging OASIS Standards with ebMS. It can also be used with business process technology including OASIS ebXML BPSS V2.0.4 and OASIS BPEL systems.

Several industry domains have declared their support for the new ebMS V3.0 including AIAG automotive group, Fujitsu and the HL7 healthcare standards community.

“This new version of ebMS will address a broader array of users including SMEs with limited connectivity and little IT management resources. The adoption of Web services standards for security and reliability will facilitate implementations over existing platforms. We believe ebMS 3.0 will become an effective and versatile B2B complement to enterprise systems and SOA deployments,” said Yasushi Ishida, Exective Architect of Software Unit, Fujitsu Limited.

For more information see

Gartner top 10 Strategic Technologies for 2008

Gartner outlined its top 10 strategic technology areas for 2008 and many roads lead to service oriented architecture.

gartner-top10.pngThe top 10 is off to the right and there aren’t any huge surprises. What’s notable are all of the SOA precursors to be found. Business process modeling (No. 3), metadata management (No. 4), mashups and composite apps (No. 6) and Web platforms (No. 7) all add up to SOA down the road. All of those aforementioned items need to be done as large companies adopt SOA.

“SOA isn’t on the list because we are looking at some of the implementation technologies for service oriented architecture,” says Gartner analyst David Cearley. For instance, business process modeling (BPM) isn’t even a technology, but it’s a necessary precursor to introducing new technology. “SOA without BPM will not deliver on its process to the business,” says David Cearley, vice president and distinguished analyst at Gartner.

Cearley argues that metadata management falls into a similar category. Without the upfront work on developing an information infrastructure SOA will stumble.
more …