1、 ETSI TS 102 829 V1.1.1 (2009-03)Technical Specification GRID;Grid Component Model (GCM);GCM Fractal Architecture Description Language (ADL)ETSI ETSI TS 102 829 V1.1.1 (2009-03)2Reference DTS/GRID-0004-3 GCM_FractalADL Keywords architecture, network, interoperability, service ETSI 650 Route des Luci
2、oles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http
3、:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the pr
4、inting on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http
5、:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and
6、 the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mar
7、k of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association
8、. ETSI ETSI TS 102 829 V1.1.1 (2009-03)3Contents Intellectual Property Rights 4g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Overall Structure of
9、the ADL . 7g34.1 Principles 7g34.1.1 Component Structure 7g34.1.2 Interfaces. 7g34.1.3 Deployment. 8g34.1.4 Behaviour 8g34.1.5 Relationship with the Management API . 8g34.2 component and definition . 8g34.3 interface 11g34.4 virtualNode . 12g34.5 exportedVirtualNode 12g34.6 composingVirtualNode 13g3
10、4.7 binding 13g34.8 content 13g34.9 attributes . 14g34.10 controller 14g34.11 behaviour 15g34.12 comment . 15g3Annex A (normative): GCM ADL Schema 16g3Annex B (informative): Examples of ADL files . 19g3B.1 Primitive components . 19g3B.2 Composite components 20g3B.3 Virtual nodes 20g3B.4 Component wi
11、th multicast interfaces . 21g3B.5 Component with gathercast interfaces 22g3B.6 Behaviour . 22g3Annex C (informative): Bibliography . 23g3History 24g3ETSI ETSI TS 102 829 V1.1.1 (2009-03)4Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declar
12、ed to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which i
13、s available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not re
14、ferenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee GRID (GRID). The present document is related to documents TS 102 827 2
15、(GCM Interoperability Deployment), TS 102 828 1 (GCM Interoperability Application Description). It discusses the Fractal ADL, a description language for software components, based on XML. Introduction The GCM has been first defined in the NoE CoreGRID (42 institutions). The GridCOMP EU project (FP6,
16、 from June 2006 to February 2009) is working to further assess and experiment with the specification. A reference Open Source implementation has been tested in the 4 previous GRID Plugtests organized from 2004 to 2008 by ETSI. The 5thGRID plugtest in 2008 directly referred to the GCM, and was open t
17、o any GCM implementation. In the present document we present a language for the description of software components. The GRID component model (GCM) aims to ease the development, deployment and maintenance of software systems. It is modular, extensible, and can be used in various programming languages
18、. The main design principle is the separation of interface and implementation. The GCM ADL is the base Architecture Description Language of this model. It is described here, in the form of an XML schema. Historically, GCM is an extension of the Fractal component model, which defines an open componen
19、t model for component systems, but has a very low support for distributed components. ETSI ETSI TS 102 829 V1.1.1 (2009-03)51 Scope The present document describes an XML based Architecture Description Language (ADL), used to define the composition of software components in distributed and parallel i
20、nfrastructures. The standard will help enterprises and laboratories to manage large-scale computer and telecom infrastructures with the necessary virtualization. Its primary audience are grid system developers who need to specify complex applications by composing existing software components. 2 Refe
21、rences References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following c
22、ases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.
23、etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references
24、, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 ETSI TS 102 828: “GRID; Grid Component Model (GCM); GCM Application Description“. 2 ETSI TS 102 827: “GRID; Grid Component Model (GCM); GCM Interoperabil
25、ity Deployment“. 2.2 Informative references The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments)
26、 applies. i.1 “The Fractal Component Model“. NOTE: Available at http:/fractal.objectweb.org/specification/index.html. i.2 CoreGrid NoE (FP6): “Basic Features of the Grid Component Model“. NOTE: Available at http:/ i.3 GCM: “A Grid extension to Fractal for Autonomous Distributed Components“, F. Baude
27、, D. Caromel, C. Dalmasso, M. Danelutto, V. Getov, L. Henrio, C. Perez. Annals of Telecommunications - The Fractal Initiative, 2008. ETSI ETSI TS 102 829 V1.1.1 (2009-03)63 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions app
28、ly: client interface: component interface that emits operation invocations component: abstraction of a software entity with a well-defined interface for both server and client parts component content: is (recursively) made of subcomponents and bindings component controller: abstract entity that embo
29、dies one aspect of a component control : a component controller manages the component with respect to a given non-functional aspect component model: specification of how components are defined and interact together control interface: component interface that manages a “non functional aspect“ of a co
30、mponent, such as introspection, configuration, and so on definition: definition is the root element of a component structure fractal: modular and extensible component model functional interface: component interface that corresponds to a provided or required functionality of a component, as opposed t
31、o a control interface gathercast interface: interface that is able to collect invocations from a set of sources and be plugged to a single destination membrane: control part of a component, it is mainly constituted of a set of Component Controllers multicast interface: interface that is able to tran
32、smit a single invocation, coming from a single source, to a set of destinations server interface: component interface that receives operation invocations virtual node: after the deployment of a GCM application, refers to a set of Nodes, which is seen as a single entity 3.2 Abbreviations For the purp
33、oses of the present document, the following abbreviations apply: ADL Architecture Description Language API Application Programming Interface FC2 Format Commun (Version 2) FIACRE Intermediate Format for the Architectures of Embedded Distributed Components GCM Grid Component Model VCE Vercors Componen
34、t Editor VN Virtual Node XML eXtensible Markup Language ETSI ETSI TS 102 829 V1.1.1 (2009-03)74 Overall Structure of the ADL 4.1 Principles The GCM ADL is an extensible language to define component architectures for the GCM component model (i.2,i.3). It is an extension of the Fractal component model
35、 i.1. Consequently, the present document can also be considered as a definition of Fractals ADL. Elements specific to GCM are the export and composition of virtual nodes, and the gathercast and multicast cardinalities. The ADL is made of a set of modules, each module defining the syntax for an archi
36、tectural “aspect“ of the language (e.g. interfaces, bindings, attributes, etc.). 4.1.1 Component Structure The main element of the ADL is the Component. The most basic component is a primitive component that is a component entirely implemented in a programming language (typically Java). Primitive co
37、mponents can be combined into composite components. More generally, a composite component is a component built by aggregating several components, primitive or composite. Composite components are characterized by the fact that their internal structure is specified. Primitive components encapsulate th
38、e business code of the application. When aggregating components into a composite component, the sub-components interfaces are bound one with another according to their respective nature and role (e.g. a components provided interface X will be bound another components required interface Y). Type comp
39、atibility can be required in order to bind together two interfaces. A component is driven through controllers. Controllers are interfaces as well, but describing actions that are irrelevant to the components main functionality. For instance, starting and stopping the component, binding it to another
40、 component, etc. The GCM Management API standardizes many of these controllers. Controllers specify the “non-functional“ features of the components. Crucial controllers allow the introspection, modification of component structure, and lifecycle control of components. The current version of the ADL d
41、oes not allow for having structured controller components in the membrane. This should be standardized in future versions. Likewise, a component may have attributes, which are key/value pairs that can be used to parameterize the component. 4.1.2 Interfaces A components relationship to the “external
42、world“ is defined by its interfaces. There are two kinds of interfaces, the ones the component provides (“server“ role), and the ones it requires (“client“ role). For instance a “calculator“ component may provide an interface consisting of “add“, “subtract“, multiply“, and “divide“, while a “spreads
43、heet“ component would require a component providing the “calculator“ interface to work. To a server interface of a composite component, a corresponding internal client interface with the same name is automatically generated. Similarly, a client interface of a composite component is automatically ass
44、ociated an internal server interface. Those interfaces allow the export of interfaces of inner components to the outside world, i.e. they are connected to complementary interfaces of inner components Interfaces have four possible cardinalities: single, collection, gathercast, or multicast. A single
45、client interface can be bound to only one server interface. A collection interface is an interface that will be duplicated several times at runtime. It can be viewed as an array of identical interfaces. A multicast interface allows one-to-many communication patterns. A client multicast interface (po
46、ssibly internal) can be plugged to many server interfaces instead of one for a single interface. The dispatch policy for the invocation can be parameterized. As ADL does not specify internal interfaces, a multicast server interface of a composite is in fact the composition of a single server interfa
47、ce and a multicast internal client interface. ETSI ETSI TS 102 829 V1.1.1 (2009-03)8A gathercast interface allows many-to-one communication patterns. A server gathercast interface can be bound from many client interfaces. Contrarily to single interfaces which necessarily transmit as many invocation
48、as they receive, gathercast interfaces can act as synchronization interfaces (synchronization barriers). The gathering and synchronization policy for the invocations can be parameterized. As ADL does not specify internal interfaces, a gathercast client interface of a composite is in fact the composi
49、tion of a gathercast internal server interface and a single client interface. 4.1.3 Deployment To enable the deployment of components on a grid environment, it is possible to specify the Virtual Node on which the component will be deployed. Additionally, the ADL can rename and compose virtual nodes of sub-components of a composite in order to expose different assemblies, and names of virtual nodes at a higher level in the hierarchy. 4.1.4 Behaviour The behaviour element allows specif
