Service Component Architecture

This product was added to computer science because of the content, defects on the quality assurance side of the editor. This is done to bring the quality of the articles from the computer science subject area to an acceptable level. Help us to eliminate the substantive shortcomings of this article and take part you in the discussion! ( ) Reason: Item is judgmental and does not explain the lemma. - Temporary interest 13:43, September 14 2009 ( CEST)

The Service Component Architecture (SCA ) is a set of specifications which describe a model of service-oriented architecture (SOA). SCA is based on open standards such as Web Services. Following the SOA thoughts are SCA components independent of a specific technology.

Partner

The following companies are working together as partners in the preparation of specifications of the Service Component Architecture: BEA Systems, Cape Clear, IBM, SpringSource, IONA Technologies, Oracle Corporation, Primeton Technologies, Progress Software, Red Hat, Rogue Wave Software, SAP AG, Software AG, Sun Microsystems, Sybase, TIBCO, Xcalia and Zend Technologies.

Definition

The published specification seems vague in many respects. But they rapidly developed and are formed out new specifications. The specifications set for SCA applications designed according to the following properties:

  • Decoupling of service implementation and deployment of the specific capabilities of the infrastructure.
  • Should work with various programming languages ​​and standards, including C , Java, COBOL, and PHP, and XML, BPEL and XSLT.
  • Must support different message constructs, in particular simple calls without reply, asynchronous communication, a conversation about multiple messages across and notifications.
  • Infrastructure facilities such as security, transactions and reliable Report should act on the encoding metadata.
  • Data should be represented as Service Data Objects.
  • After SCA principles designed components should be easily reusable.
  • Local Service calls should be more closely linked. So that the overhead of creating and parsing messages is reduced, which is intended only for transport over a network.

Further analysis

Gartner Group 2005, a short message published that comes to the conclusion that the technology contained in SCA Service Data Objects (SDO ) is experienced rapid popularity due to their maturity.

Advantages:

  • Designed for all existing Java platforms and C technologies ( However, the SCA C component model has serious flaws )
  • Less dependent on technology - for example, required to have Java or XML
  • Used SDO, the only industry standard for data access in SOA

Cons:

  • Lack of support by Microsoft reduces the relevance of SCA for a large number of potential users.
  • The specification does not address the performance of SOA applications, which remains a disturbing factor for the application.

It is claimed that SCA through an approach called activation ("activation " ) is interoperable. This method digit, compared with the older methods of " mediation" (eg JBI ) or " Invocation " (JCA ), a high degree of autonomy components safely.

SCA artifacts

The SCA Assembly Model consists of a series of artifacts. These are defined by elements in XML files. An SCA application at run time might have other non-standard representations of artifacts represented by these XML files. In addition, it can allow the dynamic configuration of systems. However, the XML files define the portable representation of the SCA artifacts.

The basic artifact is the compositum. This is also the Surrender unit within SCA and includes services that can be accessed from the outside of the. A compound containing one or more components that contain the business functionality provided from the module. Components provide their functionality as services. These can either be used by other components of the same module or they are available at entry points ( entry points ) outside of the module. Components may depend on services of other components - these dependencies are called references. References can be linked or services outside the module in particular the other modules either with services of other components of the same module. References to services outside the module are defined in the module as external services. Also included in the module are relations between references and services. These are represented by wires (wires ).

A component consists of a configured implementation, the implementation, the part-program code that implements the so-called Business Logic. The component configures the implementation has called Properties ( properties) that are held for each concrete implementation. The component can change the configuration of implementation also, by establishing the Wiring declared by the implementation of references to concrete services.

Composites are delivered within an SCA system. An SCA System represents a set of services, which in turn provide a range of business functionality, which is controlled by a single specific business unit. Example Accounting: The SCA system might cover all finance-related functions. In addition, it could contain a number of modules that deal with each defined sub-areas of accounting: one for customer accounts, another for bills. In the creation and configuration of an SCA system help subsystems. Subsystems are used to group of related compounds. Subsystems contained module components, these are configured instances of modules. Have subsystems, such as modules, entry points and external services that reflect the external services and references. Subsystems can also contain Wires that connect the module components, entry points and external services.

Implementations

  • Rogue Wave HydraSCA
  • Covansys
  • Apache Tuscany
  • Paremus Infiniflow
  • Newton
  • SCA and SDO for PHP
  • PocoCapsule
  • Trentino
Software AG TIBCO Software Business Process Execution Language Java EE Connector Architecture Covansys Corporation
724706
de