[go: nahoru, domu]
Jump to content

Service Component Architecture

From Wikipedia, the free encyclopedia

Service Component Architecture (SCA) is a software technology designed to provide a model for applications that follow service-oriented architecture principles.[1] The technology, created by major software vendors, including IBM, Oracle Corporation and TIBCO Software, encompasses a wide range of technologies and as such is specified in independent specifications to maintain programming language and application environment neutrality.[1] Many times it uses an enterprise service bus (ESB).

History

[edit]

The original partners announced on November 30, 2005 were: BEA Systems, IBM, IONA Technologies, Oracle Corporation, SAP AG, Sybase, Xcalia and Zend Technologies.[2] Additional members announced on July 26, 2006 were Cape Clear, Interface21, Primeton Technologies, Progress Software, Red Hat, Rogue Wave Software, Software AG, Sun Microsystems and TIBCO Software.[3] Siemens AG joined the collaboration of companies working on the technology on September 18, 2006.

In addition to the partners, the SCA community had some formal supporters.[4]

Definition

[edit]

On March 21, 2007, the OSOA Collaboration released the first version of specification.[5] The specifications said that an application designed with SCA should have:

  • Decoupling of application business logic from the details of its invoked service calls
  • Target services in a multitude of languages including C++, Java, COBOL, and PHP as well as XML, BPEL, and XSLT
  • The ability to work with various communications constructs including one-way, asynchronous, call-return, and notification
  • The ability to "bind" to legacy components or services, accessed normally by technologies such as Web Services, EJB, JMS, JCA, RMI, RPC, CORBA and others
  • The ability to declare (outside of business logic) the quality of service requirements, such as security, transactions and the use of reliable messaging
  • Data could be represented in Service Data Objects

SCA, therefore, was promoted to offer flexibility for composite applications, flexibly incorporating reusable components in an SOA programming style.

Marketing firm Gartner Group published a short brief that promoted the SCA and its included technology of Service Data Objects (SDO) in December 2005 .[2]

Advantages:

Disadvantages:

  • Specification does not address performance of SOA applications, which continues to be a detractor of adoption.
  • Focusing on portability (instead of interoperability),[6] making it vulnerable to repeating CORBA's mistakes.[7]

SCA was said to provide interoperability through an approach called "Activation". It is the method that provides the highest degree of component autonomy, compared to older "mediation" (e.g., JBI) or "Invocation" method used in JCA, as explained by an architect at SAP.[8]

Artifacts

[edit]

The SCA Assembly Model consists of a series of artifacts, which are defined by elements contained in XML files. An SCA runtime may have other non-standard representations of the artifacts represented by these XML files, and may allow for the configuration of systems to be modified dynamically. However, the XML files define the portable representation of the SCA artifacts.

The basic artifact is the composite, which is the unit of deployment for SCA and which holds services that can be accessed remotely. A composite contains one or more components,[9] which contain the business function provided by the module. Components offer their function as services, which can either be used by other components within the same module or which can be made available for use outside the module through Entry Points. Components may also depend on services provided by other components — these dependencies are called references. References can either be linked to services provided by other components in the same module, or references can be linked to services provided outside the module, which can be provided by other modules. References to services provided outside the module, including services provided by other modules, are defined by External Services in the module. Also contained in the module are the linkages between references and services, represented by wires.

A component consists of a configured implementation, where an implementation is the piece of program code implementing business functions. The component configures the implementation with specific values for settable properties declared by the implementation. The component can also configure the implementation with wiring of references declared by the implementation to specific target services.

Composites are deployed within an SCA System. An SCA System represents a set of services providing an area of business functionality that is controlled by a single organization. As an example, for the accounts department in a business, the SCA System might cover all financial-related functions, and it might contain a series of modules dealing with specific areas of accounting, with one for customer accounts and another dealing with accounts payable. To help build and configure the SCA System, Composites can be used as component implementations, in the same way as Java classes or BPEL processes. In other words, SCA allows a hierarchy of composites that is arbitrarily deep – such a nested model is termed recursive.

The capture and expression of non-functional requirements, such as security, is an important aspect of service definition, and affects SCA throughout the life-cycle of components and compositions. SCA provides the Policy Framework to support specification of constraints, capabilities and Quality of Service (QoS) expectations, from component design through to concrete deployment.

Transition to a standards body

[edit]

After several years of incubation under an informal industry collaboration, early (V1.0) implementations of the specification are now coming to market. The collaboration partners indicated that formal industry standardization would be the appropriate next step and announced their intentions in March 2007. The chosen Standards Development Organization is the OASIS organization, and a new OASIS Open CSA Member Section has been established.[10] Charters for six new Technical Committees (TCs) have been submitted to OASIS[11] and a Call for Participation for Technical Committee members has been issued within the OASIS organization. The Technical Committees planned to start their work in September 2007. Participation in these OASIS SCA TCs remains open to all companies, non-profit groups, governments, academic institutions, and individuals. Archives of the work will be accessible to both members and non-members, and OASIS will offer a mechanism for public comment.[12]

See also

[edit]

References

[edit]
  1. ^ a b Edwards, Mike. "Service Component Architecture". OASIS. Retrieved 7 April 2011.
  2. ^ a b Daniel Sholler; David Mitchell Smith (December 5, 2005). "New SOA Specification Will Fill Niche Among Java Users" (PDF). Gartner Group. Retrieved April 29, 2017.
  3. ^ Technology srinivas vendors extend collaboration on SOA technologies http://www.hoise.com/primeur/06/articles/monthly/AE-PR-08-06-92.html Archived 2011-07-12 at the Wayback Machine
  4. ^ OSOA Technology Supporters http://www.osoa.org/display/Main/Current+OSOA+Supporters+Community
  5. ^ "Service Component Architecture Specifications". Open SOA Collaboration web site. Archived from the original on October 12, 2007. Retrieved April 29, 2017.
  6. ^ [1] Archived 2008-07-05 at the Wayback Machine SCA & SDO, the next Corba?
  7. ^ "ACM Queue - the Rise and Fall of CORBA: The story behind this once-promising distributed computing technology-why it fell short, and what we can learn from it". Archived from the original on 2008-12-02. Retrieved 2011-04-08. The rise and fall of CORBA
  8. ^ "community.user: Comparing SCA, Java EE and JBI | SCN". Sdn.sap.com. 2005-12-12. Archived from the original on 2012-12-17. Retrieved 2013-06-16.
  9. ^ Bell, Michael (2008). "Service-Oriented Conceptualization". Service-Oriented Modeling: Service Analysis, Design, and Architecture. Wiley & Sons. p. 3. ISBN 978-0-470-14111-3.
  10. ^ "OASIS Open CSA Member Section for SCA".
  11. ^ "Six Technical Committees Proposed for the OASIS Open CSA Member Section".
  12. ^ "Six OASIS Committees Form to Standardize Service Component Architecture (SCA) for SOA".

Further reading

[edit]
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Service_Component_Architecture&oldid=1197881958"