Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Search results
Create the page "SMILA/Processing Service" on this wiki! See also the search results found.
- ...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 API4 KB (516 words) - 03: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 co32 KB (4,383 words) - 05: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) - 07: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 devel23 KB (2,932 words) - 06: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) - 11: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 proces12 KB (1,766 words) - 07: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 either6 KB (990 words) - 07: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>. Pr9 KB (1,401 words) - 08: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 fini21 KB (3,427 words) - 11: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 tas18 KB (2,819 words) - 03: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 error7 KB (1,202 words) - 10: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) - 11: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 work6 KB (947 words) - 09: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, without4 KB (648 words) - 05: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) - 09: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 processing13 KB (2,068 words) - 11: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 service12 KB (1,829 words) - 04: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) - 11: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 d19 KB (3,066 words) - 05: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 service16 KB (2,443 words) - 05:13, 26 May 2014
- == Scripting SMILA using JavaScript == {{note| Available since SMILA 1.3!}}18 KB (2,625 words) - 03: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 service17 KB (2,244 words) - 04: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) - 11:04, 9 April 2015
- = ScriptProcessorWorker (bundle org.eclipse.smila.scripting) = {{note| Available since SMILA 1.3!}}9 KB (1,319 words) - 07: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) - 09:33, 8 April 2015