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
  • A concept of service registry for groupping services ...found in [[http://www.eclipsezone.com/eclipse/forums/t96740.html]] and for service lookup in [[http://www.eclipsezone.com/eclipse/forums/t97690.rhtml]].
    7 KB (823 words) - 09:40, 17 November 2008
  • | [[SMILA/Specifications/CrawlerAPIDiscussion09|Crawler API Discussion Version 0.9]] | [[SMILA/Specifications/DeltaIndexingAndConnectivtyDiscussion09|DeltaIndexing & Conn
    1 KB (147 words) - 03:15, 21 April 2011
  • ...ithin complex enterprise applications that use loosely\-coupled designs or service\-oriented architectures" ...for C and java that allows timing information associated with each step in processing a transaction to be logged to a remote server for later analysis
    6 KB (876 words) - 10:32, 15 August 2008
  • [[Category:SMILA]] the current implementation for the [[SMILA/Documentation/DeltaIndexingManager | DeltaIndexingManager]] has several pro
    14 KB (1,671 words) - 01:56, 17 October 2009
  • ...different types and complexity levels for the integration of components in SMILA. Due to its architecture SMILA allows for the easy integration of third-party components into its framewor
    11 KB (1,674 words) - 12:58, 23 October 2012
  • ...MILA/Howto_integrate_a_component_in_SMILA| How to integrate a component in SMILA]]. It may be helpful to first take a look at the SMILA [[SMILA/Development_Guidelines|Development guidelines]] as many topics that are bey
    18 KB (2,727 words) - 05:26, 27 November 2014
  • Smila is using a [http://logging.apache.org/log4j/ Apache log4j]. File EILF.log where registers a log information for Smila contains too much not the helpful information. Most of all messages arrive
    19 KB (3,009 words) - 11:33, 17 November 2008
  • == What is SMILA? == SMILA is a ''framework'' for creating scalable server-side systems that process l
    7 KB (1,081 words) - 10:34, 22 September 2014
  • ...o pass data to external webservices. It is not required for the usage of [[SMILA/Glossary#P|pipelets]]. ...onfiguration file of the processing service found at <tt>org.eclipse.smila.processing.bpel/processor.properties</tt>. If you wish to write data to attributes you
    5 KB (812 words) - 08:28, 24 January 2012
  • This page is dedicated to general requirements posed on SMILA as a whole framework. ...SMILA should be the use of standards. Since one of major goals is to make SMILA open as much as possible to other contributors and vendors, established and
    10 KB (1,524 words) - 16:26, 10 October 2008
  • The core of the SMILA framework consists of a pipeline where data is pushed into a queue whence ...ation for the storage point from where data will be loaded before the BPEL processing (“Input” storage point);
    16 KB (2,431 words) - 07:06, 24 January 2012
  • Some Smila components have to be managed. See [[SMILA/Workflow Overview |Workflow Smila]].
    5 KB (650 words) - 05:06, 4 May 2009
  • ...only the Id and the metadata. To persist attachments one has to use the [[SMILA/Documentation/Binary_Storage|Binary Storage]]. {{note| Unused since SMILA 0.9
    5 KB (667 words) - 04:01, 24 January 2012
  • ...lets.MimeTypeIdentifyPipelet| SMILA/Documentation/Bundle_org.eclipse.smila.processing.pipelets ]]. ...[http://build.eclipse.org/rt/smila/javadoc/current/index.html?org/eclipse/smila/common/mimetype/MimeTypeIdentifier.html MimeTypeIdentifier here]
    3 KB (393 words) - 06:04, 1 February 2013
  • ...page. By this we at least provide a working solution. When wanting to use SMILA for large scale application including full functionality in regard to XS th :::# request a RecordStoreQuery OSGi service that might not be there, depending on ur config?
    28 KB (4,131 words) - 03:14, 13 May 2010
  • {{note|This is deprecated for SMILA 1.0, the connectivity framework is still functional but will aimed to be re ...on of each record and can determine if a record has changed since its last processing. This decision is based on a hash value provided by a crawler. How such has
    6 KB (952 words) - 04:36, 24 January 2012
  • == Pipelet: org.eclipse.smila.security.processing.SampleSecurityConverterPipelet == The pipelet uses the service <tt>a org.eclipse.smila.security.SecurityResolver</tt>, which is used to resolve groups and user na
    3 KB (347 words) - 10:52, 23 January 2012
  • {{note|This is deprecated for SMILA 1.0, the JMX management framework is still functional but it's planned to r ...a's built in JConsole and to handle the JMXClient which features access to SMILA commands via batch files.
    10 KB (1,524 words) - 02:12, 5 July 2012
  • [[Category:SMILA]] The [[SMILA/Documentation/Usage of Blackboard Service]] has been updated accordingly
    9 KB (1,444 words) - 05:55, 30 September 2009
  • ...cuted pipeline that prepare the security information to be useable by some service (e.g. for the former mentioned use case the security information is stored Authentication (e.g. login to a SMILA based web application) is not in the scope of this document.
    11 KB (1,609 words) - 04:09, 16 January 2012
  • {{note|This is deprecated for SMILA 1.0, the connectivity framework is still functional but will aimed to be re ...supported: Agents and Crawlers. To integrate some new datasource type into SMILA just a new Agent or Crawler has to be implemented.
    4 KB (561 words) - 04:35, 24 January 2012
  • ...nd related parts of SMILA. This includes the query and result helpers, the processing of search requests internally, and the sample servlet used to create a simp ...browser to go to [http://localhost:8080/SMILA/search http://localhost:8080/SMILA/search] and search on the index:
    25 KB (3,914 words) - 07:58, 28 November 2014
  • SMILA currently comes with two types of Agents, each for a different datasource t ...ethod <tt>run()</tt> of the <tt>Runnable</tt> interface which contains the processing logic of the agent.
    8 KB (1,257 words) - 02:56, 21 April 2011
  • # Exemplary Policy processing: [[Swordfish_Documentation:_User_Stories:_Service_Developer#S059 | S059]] # Service Browser for BPEL Editor: [[Swordfish_Documentation:_User_Stories:_BPEL_Deve
    3 KB (505 words) - 09:40, 14 May 2009
  • * if we do not want SMILA to process and index the compound records themselves we could delete the re ...the class CrawlThread). It should also be available in the AgentController processing logic although we currently do not have an Agent that provides compound rec
    6 KB (891 words) - 09:58, 2 June 2009
  • == Creating Webservices in SMILA from OSGi services using JAX-WS == SMILA includes a simple tool now that make it possible to publish OSGi services w
    3 KB (553 words) - 08:24, 9 February 2010
  • [[Category:SMILA]] ...discussion is still happening on the [http://dev.eclipse.org/mhonarc/lists/smila-dev/msg00608.html dev list].
    11 KB (1,769 words) - 07:09, 9 October 2009
  • [[Category:SMILA]] # the SRS defines boundaries between which, processing of multiple PRs for one given resource can be done concurrently and in any
    9 KB (1,662 words) - 15:43, 7 October 2009
  • [[Category:SMILA]] # the SN is transient and not part of the actual record. its a processing meta information such as DEL, ADD.
    2 KB (437 words) - 07:27, 9 October 2009
  • == Automatic Ontology Extraction with SMILA [[Media:Novakovic - SMILA - The Integration Framework.pdf|(slides)]] == ...y integrating an entity extraction web service (provided by OpenCalais) in SMILA.
    11 KB (1,651 words) - 04:00, 4 December 2009
  • ...is intended to serve as a cross reference to the SMILA manual based on the SMILA ReST API. It lists all URLs of the ReST API and links them to the manual pa * '''<tt>/smila/</tt>''': Main entry page: system state overview and links to the other API
    4 KB (516 words) - 02:16, 13 April 2015
  • == Configuration and Usage of the Jetty HTTP server embedded in SMILA == ...>. When the bundle is activated it starts the OSGi service <tt>org.eclipse.smila.http.server.HttpService</tt> which in turn creates a Jetty server from a co
    32 KB (4,383 words) - 04:54, 18 July 2014
  • == VisitedLinks: An auxiliary Service for crawler workers == ...information even when the crawler worker is running on multiple nodes in a SMILA cluster.
    4 KB (675 words) - 06:56, 19 January 2012
  • .... database, connectors, etc.) for the new SMILA importing framework (see [[SMILA/Documentation/Importing/Concept|Importing Concept]] for more information ab * Set up your development environment, see [[SMILA/Development Guidelines/Howto set up dev environment|How to set up the devel
    23 KB (2,932 words) - 05:14, 10 January 2013
  • = Bundle org.eclipse.smila.objectstore = ...[http://build.eclipse.org/rt/smila/javadoc/current/index.html?org/eclipse/smila/objectstore/package-summary.html JavaDoc] for specific information.
    8 KB (1,135 words) - 10:40, 23 January 2012
  • ...is now really ready for "the big business" which means handling huge data processing in optimal way by bulking data and offering horizontal and vertical scale-u ...th the current development stream, RAP integrates seamlessly with the OSGi service platform. This allows to start separate RAP applications in a single proces
    12 KB (1,766 words) - 06:34, 23 November 2011
  • ...turn generates tasks and decides which task should be processed by which [[SMILA/Glossary#W|worker]] and when. ...the data which have been extracted from an external data source (e.g. a [[SMILA/Documentation/Importing/Concept|Crawler]] worker). The workflow ends either
    6 KB (990 words) - 06:52, 8 January 2013
  • ...ion/JobRuns|job run]]. For jobs running in "standard" mode, the actual job processing is triggered with every new object that is dropped into the bucket connecte ...he system, in which case they are located at <tt>configuration/org.eclipse.smila.jobmanager/jobs.json</tt> and are marked with <tt>"readOnly": true</tt>. Pr
    9 KB (1,401 words) - 07:19, 8 January 2013
  • ...First, the job must be started to get a so called job run. How the actual processing is then triggered, depends on the mode of the job run. ...nput bucket, which the start worker produces from other sources like the [[SMILA/Documentation/Bulkbuilder|Bulkbuilder]]). They continue until they are fini
    21 KB (3,427 words) - 10:33, 22 September 2014
  • ...produced as initial tasks or as follow-up tasks when workers finish their processing of their current task. ...But redelivery of tasks is the exception to the rule, usually during task processing we do not expect errors to happen. There are some rare cases in which a tas
    18 KB (2,819 words) - 02:56, 22 July 2014
  • ...r service provides all the managements of [[SMILA/Glossary#T|tasks]] and [[SMILA/Glossary#D|data objects]] to be consumed and produced by the worker so that ...fies the worker about task cancellation. When the worker finished the task processing, the WorkerManager cares about finishing the task: successfully if no error
    7 KB (1,202 words) - 09:42, 8 January 2013
  • = Bulkbuilder (bundle org.eclipse.smila.bulkbuilder) = ...ry#W|worker]] for data to an [[SMILA/Glossary#W|asynchronous workflow]] in SMILA.
    7 KB (1,172 words) - 10:50, 23 January 2012
  • = PipelineProcessorWorker (bundle org.eclipse.smila.processing.worker) = ...a dedicated pipeline processing implementation. However, in SMILA we use [[SMILA/Documentation/BPEL_Workflow_Processor|BPEL pipelines]] for synchronous work
    6 KB (947 words) - 08:07, 29 October 2014
  • = PipeletProcessorWorker (bundle org.eclipse.smila.processing.worker) = The PipeletProcessorWorker is a [[SMILA/Glossary#W|worker]] designed to execute a single pipelet directly, without
    4 KB (648 words) - 04:54, 5 December 2013
  • ...a record has changed since the last import run and needs to be sent to the processing job again, e.g. to update the index. ...r possible values that select one of two behaviours for this worker (see [[SMILA/Documentation/Importing/Concept#Delta_Delete|DeltaDelete]] for an overview)
    6 KB (972 words) - 08:59, 20 February 2012
  • ...rs can use same programming model for creating crawler components than for processing workers. * same control and monitoring APIs for crawling and processing
    13 KB (2,068 words) - 10:23, 8 January 2013
  • ...ystem. For a big picture and the worker's interaction have a look at the [[SMILA/Documentation/Importing/Concept | Importing Concept]]. ...''(req.)'' value for attribute <tt>_source</tt>, needed e.g. by the delta service
    12 KB (1,829 words) - 03:57, 19 February 2015
  • The jobmanager workflow processing is based on the processing of tasks by the workers. Tasks for a worker are generated based on changes ==== TaskGenerator as OSGi service ====
    7 KB (1,147 words) - 10:03, 8 January 2013
  • ...erver. For a big picture and the worker's interaction have a look at the [[SMILA/Documentation/Importing/Concept | Importing Concept]]. ...e crawler additionally reads the crawled sites' <tt>robots.txt</tt>. See [[SMILA/Documentation/Importing/Crawler/Web#User-Agent_and_robots.txt|below]] for d
    19 KB (3,066 words) - 04:51, 21 October 2014
  • ...abase. For a big picture and the worker's interaction have a look at the [[SMILA/Documentation/Importing/Concept | Importing Concept]]. ...''(req.)'' value for attribute <tt>_source</tt>, needed e.g. by the delta service
    16 KB (2,443 words) - 04:13, 26 May 2014
  • == Scripting SMILA using JavaScript == {{note| Available since SMILA 1.3!}}
    18 KB (2,625 words) - 02:57, 9 April 2015
  • ...er schedulers. We are planning to integrate an own scheduling component in SMILA in the future.}} ...''(req.)'' value for attribute <tt>_source</tt>, needed e.g. by the delta service
    17 KB (2,244 words) - 03:21, 2 February 2015
  • ...achine, but this is not new, because you also have this with a single-node SMILA.) The following steps describe how to set up SMILA on multiple cluster nodes.
    8 KB (1,106 words) - 10:04, 9 April 2015
  • = ScriptProcessorWorker (bundle org.eclipse.smila.scripting) = {{note| Available since SMILA 1.3!}}
    9 KB (1,319 words) - 06:08, 20 November 2014
  • It all depends on the solr-config.json in which way smila is going to connect to solr. Here is an example showing possible configurat "EmbeddedSolrServer.solrHome":"configuration\\org.eclipse.smila.solr\\solr_home",
    73 KB (9,704 words) - 08:33, 8 April 2015

Back to the top