SOA models and frameworks
According to an article (2007-05-22), the market share of SOA engines was IBM 53%, Microsoft 7%. "Other vendoers including BEA, Tibco and Sun Microsystems' Seebeyond each each logged in at 2 to 3 per cent." The article comments that the report attributes it to the fact that all IBM "products have an SOA engine baked in natively. Many competing products currently use adapters that slap on SOA functionality to their exiting middleware."
- SCA (Service Component Architecture) by Open SOA (based on WS and BPEL)
- Fusion Middleware by Oracle (details are not known but apprently SCA-based)
- SSA (Shared Services Architecture) by Hewlett-Packard (not an Open SOA member)
- JBI (Java Business Integration) specification and Open ESB (Enterprise Service Bus) 2.0 by Sun Microsystems (an Open SOA member but JBI/ESB are not SCA-based)
- IBF (Information Bridge Framework) by Microsoft (not an Open SOA member, and it is a Desktop solution)
- Web Services Policy by W3C (an SOA support technology, originaly jointly developed by IBM and Microsoft)
- IBM SOA Foundation and WebSphere Business Modeler (What "standard" the SOA and the Modeler use are not clear)
- ServiceMix
- Celtix
- JBoss Enterprise Middleware System (JEMS) and JBossESB (v 4.2 MR2 as of 2007-05-25, based on Rosetta ESB which was running for 3 years)
- LAMS Tool Contract by LAMS Foundation
SCA & SDOs
SCA SCA (Service Component Architecture) and SDO (Service Data Object) Project were developed by Open SOA. Open SOA states that it is an informal group of industry leaders (see Project Partners for SCA and Open SOA supporters), including e.g. IBM, Sun Microsystems, Red Hut, Oracle, BEA, Sybase, SAP to name a few (but no Microsoft).
SCA and SDOs define some components used in an SOA.
SCA
SCA is a set of standards. SCA is not a full SOA framework or an SOA-based application solution. Rather, it provides a hiearchichal composite structures of heterogenous services: e.g. a Component is a composite of Services, then multiple Components may form an SCA Domain (which is a composite of Components).
A part of the standard defines how to use Web Services. Therefore, SCA and BPEL can be used as complementary technologies. On the SCA site, there is an article called "WS-BPEL Client and Implementation model". Other documents define, for example, C++ and Java bindings.
SDO
SDO is also a standard defining SDOs, which "are designed to simplify and unify the way in which 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."
Comparison of SCA and JBI
Open SOA: Relationship of SCA and JBI
SAP Labs Palo Also (2005): Comparing SCA, Java EE and JBI
JBoss Enterprise Middleware system (JEMS)
JEMS consists of the folowing components (figure taken from rh_soa_strategy_04_07.pdf):

The SOA platform comprises of JBI and JBossESB. See more details in ESB (Enterprise Service Bus) and SOA.
