Difference between revisions of "SMILA/Glossary"
|Line 34:||Line 34:|
== E ==
== E ==
* '''[http://www.eclipse.org/ Eclipse]''' - Eclipse is an open source community whose projects are focused on building an open development platform comprised of extensible frameworks, tools and runtimes for building, deploying and managing software across the lifecycle.
* '''[http://www.eclipse.org/ Eclipse]''' - Eclipse is an open source communitywhose projects are focused on building an open development platform comprised of extensible frameworks, tools and runtimes for building, deploying and managing software across the lifecycle.
* '''[http://www.eclipse.org/equinox/ Equinox]''' - a technology from [http://www.eclipse.org|
* '''[http://www.eclipse.org/equinox/ Equinox]''' - a technology from [http://www.eclipse.org| Eclipse] implementing the [[#O|OSGi]] specification. Not only delivering a high performance class loading mechanism Equinox also provides an environment for managing component dependencies.
== I ==
== I ==
Revision as of 03:15, 29 September 2008
- Agent - An agent is a component of the connectivity framework that monitors a data source for changes. If a change occurs (e.g. objects are created, deleted, or changed) it creates a record out of the object and sends it to SMILA.
- Annotation - Annotations are additional information on attributes or attachments. Annotations can have annotations themselves.
- Aperture - Aperture is a Java framework for extracting and querying full-text content and metadata from various information systems (e.g. file systems, web sites, mail boxes) and the file formats (e.g. documents, images) occurring in these systems.
- Attachment - Attachments are parts of records used to store large binary data such as document content.
- Attribute - Attributes are parts of records and contain simple data objects that are easily represented in XML, such as String, Integer, Float, and Date.
- Blackboard or blackboard service - The blackboard service manages SMILA records during processing in a SMILA component (connectivity, workflow processor). In addition it hides the handling of record persistence from these components. For a complete description see Usage of Blackboard Service.
- BPEL - BPEL is an XML-based language defining several constructs to write business processes. It defines a set of basic control structures like conditions or loops as well as elements to invoke web services and receive messages from services. It relies on WSDL to express web services interfaces. Message structures can be manipulated, assigning parts or the whole of them to variables that can in turn be used to send other messages.
- Crawler - A crawler is a component of the connectivity framework that actively crawls a data source, creates records out of the objects found in the data source and sends them to SMILA (e.g. FileSystemCrawler or WebCrawler).
- Delta indexing - Delta indexing is also known as incremental or generation based indexing.
- DFP - The Data Flow Process is a set of processing steps. These steps cover the following aspects and is described in the data flow process description:
- Storage descriptions
- Extraction of messages from the queue
- Process based information handling (e.g. splitting, routing, ...)
- Data annotation through BPEL
- DFPD - The Data Flow Process Description is a set of process related configuration files. Files in this set are optional. The following components are contained in the DFPD:
- Source/target references (e.g. queue)
- References to different storages or collections
- BPEL (change and delete process in several files organized in system/data processes)
- Eclipse - Eclipse is an open source community, whose projects are focused on building an open development platform comprised of extensible frameworks, tools and runtimes for building, deploying and managing software across the lifecycle.
- Equinox - Equinox is a base technology from Eclipse implementing the OSGi specification. Not only delivering a high performance class loading mechanism Equinox also provides an environment for managing component dependencies.
- ID - An ID identifies a Record in SMILA and is part of a Record. IDs are complex objects, aggregated of various keys (data source Id, object IDs within the data source, element and/or fragment Ids )
- IRM - Information Reference Model
- ODE - Apache ODE (Orchestration Director Engine) executes business processes written following the BPEL/WS-BPEL standard. It talks to web services, sending and receiving messages, handling data manipulation and error recovery as described by your process definition. It supports both long and short living process executions to orchestrate all the services that are part of your application.
- OSGi - The OSGi specification is about manageing a component based software system. It defines an in-VM Service Oriented Architecture (SOA) for networked systems. An OSGi Service Platform provides a standardized, component-oriented computing environment for cooperating networked services. This architecture significantly reduces the overall complexity of building, maintaining and deploying applications.
- Pipelet - A Pipelet is a reusable Component (POJO) in a BPEL workflow used to process data contained in Records. See Pipelets and ProcessingServices for details.
- Pipeline - A Pipeline is the definition of a BPEL process (or workflow) that orchestrates Pipelets, ProcessingServices and other BPEL services (e.g. webservices)
- ProcessingService - A ProcessingService is a reusable Component (OSGi service) in a BPEL workflow used to process data contained in Records. See Pipelets and ProcessingServices for details.
- Record - A Record is a sole element in SMILA that contains data to process (e.g. content and metadata of a document). Every Record has an ID and it can contain Attributes, Attachments and Annotations.
- SCA - Service Component Architecture is a set of specifications which describe a model for building applications and systems using a Service-Oriented Architecture. SCA extends and complements prior approaches to implementing services, and SCA builds on open standards such as Web services. The SCA programming model is highly extensible and is language-neutral. Go to SCA and Tuscany for discussing.
- SDO - Service Data Objects 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. The SDO programming model is language neutral.
- SOA - Service Oriented Architecture is a computer systems architectural style for creating and using business processes, packaged as services, throughout their lifecycle. SOA also defines and provisions the IT infrastructure to allow different applications to exchange data and participate in business processes. These functions are loosely coupled with the operating systems and programming languages underlying the applications.
- Surrogate Process - A surrogate process is a process that embeds several components. Additionally this process adds further functionality to these components (e.g. runtime functionality, error prevention, transactions, manageability ...). In the SMILA application surrogate processes als add business processes and further features (e.g. callability from external processes or applications...).
- STP - SOA Tools Platform is an eclipse open source project that builds frameworks and exemplary extensible tools that enable the design, configuration, assembly, deployment, monitoring, and management of software designed around a Service Oriented Architecture (SOA). An interesting subproject is the SCA Composite Designer.
- Tuscany - Apache Tuscany is an implementation of the SCA specification 1.0. It is available for Java and C++. It also supports SDO specification 2.1 for both Java and C++. Go to SCA and Tuscany for discussing.
- Workflow - see Pipeline
- WSDL - WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate.