Skip to main content
Jump to: navigation, search

Search results

  • The pages linked here describe concepts to be implemented in SMILA and serve as places for discussions of these concepts. They are '''not''' i * Changes in 0.8: [[SMILA/Documentation/2011.Simplification|Simplification of SMILA concepts]]
    3 KB (306 words) - 09:23, 24 January 2012
  • ...us workflow]] associated with a certain [[#W|worker]] that does the actual processing. ...see [[SMILA/Documentation/Usage_of_Blackboard_Service|Usage of Blackboard Service]].
    9 KB (1,455 words) - 02:09, 7 April 2015
  • This page describes the data model used in SMILA to represent data objects (records) in workflows. ...to the Controller (a valid deployment scenario from the very beginning of SMILA) ... what should SCA do there? So, in general we should design our interfac
    16 KB (2,487 words) - 11:00, 11 November 2008
  • Design a service to ease management of SMILA records during workflow processing. ...by default a configurable process for indexing/storage at the end of BPEL processing or we use pipelets for this case. Please share your thoughts.
    22 KB (3,191 words) - 04:53, 19 January 2012
  • ...ng internal structures, etc). DS also defines a method to be called when a service is deactivated that can be used for cleaning up. The two methods must have ...that specifies the name of this pipelet. The name must be unique for each service in a single VM and is defined in the DS component description. The pipelet
    17 KB (2,547 words) - 03:56, 16 January 2012
  • * [[SMILA/5_Minutes_Tutorial|Installing and Running (5 Minutes Tutorial)]] * [[SMILA/Documentation/HowTo|HowTos]]
    8 KB (849 words) - 02:25, 13 April 2015
  • ...g to enable you to create at least simple BPEL processes for being used in SMILA. ...that describes the main configuration. This file can contain the following SMILA specific properties:
    16 KB (2,359 words) - 07:07, 27 June 2014
  • == SMILA Data Model == * Implementation bundle: <tt>org.eclipse.smila.datamodel</tt>
    22 KB (3,180 words) - 07:23, 11 April 2013
  • ...page describes the SMILA pipelets provided by bundle <tt>org.eclipse.smila.processing.pipelets</tt>. ...s in this bundle support the configurable error handling as described in [[SMILA/Development_Guidelines/How_to_write_a_Pipelet#Implementation]]. When used i
    46 KB (6,289 words) - 09:44, 9 March 2016
  • == Putting the Semantics in SMILA == ...nt to an ontology that does not even meet their needs. The main purpose of SMILA is to provide a stable, reliable, scalable and performant infrastructure fo
    18 KB (2,831 words) - 11:38, 17 June 2013
  • ...e service]] on demand and write it back if processing is done (however, in SMILA 1.0 we do not use the RecordStorage by default anymore). ...configurable there, or it depends on if storage services are active in the SMILA application. For the user of the blackboard (the pipelet, usually), it shou
    3 KB (460 words) - 04:38, 19 December 2014
  • ...ish to [[SMILA/Howto_integrate_a_component_in_SMILA|add functionality]] to SMILA. ...uses a different pipelet instance. For more information take a look at [[SMILA/Documentation/Pipelets|Pipelets]].
    12 KB (1,754 words) - 04:30, 19 December 2014
  • == Bundle: <tt>org.eclipse.smila.aperture.pipelets.AperturePipelet</tt> == ...ntification is done inside the pipelet using a <tt>MimeTypeIdentifier</tt> service.
    14 KB (1,997 words) - 05:57, 11 January 2013
  • == Class: <tt>org.eclipse.smila.aperture.ApertureMimeTypeIdentifier</tt> == Located in bundle: <tt>org.eclipse.smila.aperture</tt>
    3 KB (384 words) - 05:57, 11 January 2013
  • ...o easily integrate data from external systems via Agents and Crawlers. The processing logic of the data is implemented once in so called Controllers, which use a ...rk with it's plugable components (Agents/Crawlers) and relationship to the SMILA entry point Connectivity Module.
    20 KB (3,091 words) - 04:54, 19 January 2012
  • ...the Lucene Query Service or more genereal using some scheduling service of SMILA. ...ctivity Manager is the single point of entry for information (data) in the SMILA. It's functionality is devided into several Sub-Components for better modul
    16 KB (2,484 words) - 07:17, 13 August 2008
  • The processing of the various types of compound objects and creation of "CompoundCrawlers" <CompoundHandler mimetype="application/zip" class="org.eclipse.smila.irm.compoundmanagement.ZipCompoundHandler">
    10 KB (1,413 words) - 02:01, 12 May 2009
  • ...ffer any advantages (except that we will make use of SCA in other parts of SMILA and so the it would be more homogeneous). What other possibilities do we ha ...ched. There may be simple cases, where the configuration is equal, but the processing of the crawled information usualy leads to additional index fields. Also no
    15 KB (2,447 words) - 09:23, 24 January 2012
  • [[Image:Architecture Overview - Service Level.png]] Outdated information could be found at: [[SMILA/Project_Concepts/Outdated]]
    7 KB (997 words) - 08:38, 5 October 2008
  • ...their product development by using ready to use components. That means the SMILA is used to complete existing products. ...on scenarios are inspired by enterprise needs. For some of these scenarios SMILA runtime configurations/installations will be provided.
    8 KB (1,170 words) - 07:43, 26 March 2009

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Copyright © Eclipse Foundation, Inc. All Rights Reserved.