Jump to: navigation, search

Difference between revisions of "SMILA/5 Minutes Tutorial"

(JRE)
(Start the indexing job run)
 
(9 intermediate revisions by one other user not shown)
Line 20: Line 20:
 
<pre>
 
<pre>
 
/<SMILA>
 
/<SMILA>
  /about_files
+
   /configuration  
   /configuration
+
  /features
+
  /jmxclient
+
  /plugins
+
  /workspace
+
  .eclipseproduct
+
 
   ...
 
   ...
 
   SMILA
 
   SMILA
Line 36: Line 30:
  
 
==== JRE ====
 
==== JRE ====
You will have to provide a JRE executable to be able to run SMILA. The JVM version should be at least Java 5. You may either:
+
You will have to provide a JRE executable to be able to run SMILA. The JVM version should be Java 7 (or newer). You may either:
 
* add the path of your local JRE executable to the PATH environment variable <br>or<br>
 
* add the path of your local JRE executable to the PATH environment variable <br>or<br>
 
* add the argument <tt>-vm <path/to/jre/executable></tt> right at the top of the file <tt>SMILA.ini</tt>. <br>Make sure that <tt>-vm</tt> is indeed the first argument in the file, that there is a line break after it and that there are no leading or trailing blanks. It should look similar to the following:
 
* add the argument <tt>-vm <path/to/jre/executable></tt> right at the top of the file <tt>SMILA.ini</tt>. <br>Make sure that <tt>-vm</tt> is indeed the first argument in the file, that there is a line break after it and that there are no leading or trailing blanks. It should look similar to the following:
Line 48: Line 42:
  
 
==== Linux ====
 
==== Linux ====
When using the Linux distributable of SMILA, make sure that the files <tt>SMILA</tt> and <tt>jmxclient/run.sh</tt> have executable permissions. If not, set the permission by running the following commands in a console:  
+
When using Linux, make sure that the file <tt>SMILA</tt> has executable permissions. If not, set the permission by running the following commands in a console:  
 
<tt>
 
<tt>
 
  chmod +x ./SMILA
 
  chmod +x ./SMILA
chmod +x ./jmxclient/run.sh
 
 
</tt>
 
</tt>
  
 
==== MacOS ====
 
==== MacOS ====
When using MAC switch to <tt>SMILA.app/Contents/MacOS/</tt> and set the permission by running the following command in a console:
+
When using MAC, switch to <tt>SMILA.app/Contents/MacOS/</tt> and set the permission by running the following command in a console:
 
<tt>
 
<tt>
 
  chmod a+x ./SMILA
 
  chmod a+x ./SMILA
Line 61: Line 54:
  
 
=== Start SMILA ===
 
=== Start SMILA ===
To start the SMILA engine, simply double-click the <tt>SMILA</tt> executable. Alternatively, open a command line, navigate to the directory where you extracted the files to, and execute the <tt>SMILA</tt> executable. Wait until the engine has been fully started.
+
To start SMILA, simply start the <tt>SMILA</tt> executable.  
  
You can tell if SMILA has fully started if the following line is printed on the OSGI console: <tt>HTTP server started successfully on port 8080</tt> and you can access SMILA's REST API at [http://localhost:8080/smila/ http://localhost:8080/smila/].
+
You can see that SMILA has fully started if the following line is printed on the OSGI console:  
 +
<tt>
 +
  ...
 +
  HTTP server started successfully on port 8080
 +
</tt>  
 +
and you can access SMILA's REST API at [http://localhost:8080/smila/ http://localhost:8080/smila/].
  
When using MAC, navigate to <tt>SMILA.app/Contents/MacOS/</tt> in terminal, then start with <tt>./SMILA</tt>
+
If it doesn't work, check the log file (SMILA.log) for possible errors.
 
+
Before continuing, [[SMILA/FAQ#How_can_I_see_that_SMILA_started_correctly.3F|check the log file]] for possible errors.
+
  
 
=== Stop SMILA ===
 
=== Stop SMILA ===
  
To stop the SMILA engine, type <tt>close</tt> into the OSGI console and press ''Enter'':
+
To stop SMILA, type <tt>close</tt> into the OSGI console and press ''Enter'':
  
<source lang="text">
+
<tt>
osgi> close
+
  osgi> close
</source>
+
</tt>
  
For further OSGI console commands, enter <tt>help</tt>:
+
== Start Indexing Job and Crawl Import ==
  
<source lang="text">
+
Now we're going to crawl and process the SMILA Eclipsepedia pages, Finally we index and search them by using the embedded [[SMILA/Documentation/Solr|Solr integration]].
osgi> help
+
</source>
+
  
== Install a REST client ==
+
=== Install a REST client ===
  
 
We're going to use SMILA's REST API to start and stop jobs, so you need a REST client. In [[SMILA/Documentation/Using_The_ReST_API#Interactive_Tools|REST Tools]] you find a selection of recommended browser plugins if you haven't got a suitable REST client yet.
 
We're going to use SMILA's REST API to start and stop jobs, so you need a REST client. In [[SMILA/Documentation/Using_The_ReST_API#Interactive_Tools|REST Tools]] you find a selection of recommended browser plugins if you haven't got a suitable REST client yet.
  
== Start Indexing Job and Crawl Import ==
+
=== Start the indexing job run ===
  
Now we're going to crawl the SMILA Eclipsepedia pages and index them using the embedded [[SMILA/Documentation/Solr|Solr integration]].
+
We are going to start the predefined indexing job "indexUpdate" based on the predefined asynchronous workflow with the same name. This indexing job will process the imported data.
 
+
=== Start indexing job run ===
+
 
+
We are going to start the predefined indexing job "indexUpdate" based on the predefined asynchronous "indexUpdate" workflow. This indexing job will process the imported data.
+
  
 
Use your favorite REST Client to start a job run for the job "indexUpdate":
 
Use your favorite REST Client to start a job run for the job "indexUpdate":
  
<source lang="javascript">
+
<tt>
#Request
+
  POST http://localhost:8080/smila/jobmanager/jobs/indexUpdate/
POST http://localhost:8080/smila/jobmanager/jobs/indexUpdate/
+
</tt>
</source>
+
  
 
Your REST client will show a result like this:
 
Your REST client will show a result like this:
 +
<tt>
 +
{
 +
  "jobId" : "20110901-121343613053",
 +
  "url" : "http://localhost:8080/smila/jobmanager/jobs/indexUpdate/20110901-121343613053/"
 +
}
 +
</tt>
  
<source lang="javascript">
+
You will need the job run id ("jobId") later on to finish the job run. The job run Id can also be found via the monitoring API for the job:
#Response
+
{
+
  "jobId" : "20110901-121343613053",
+
  "url" : "http://localhost:8080/smila/jobmanager/jobs/indexUpdate/20110901-121343613053/"
+
}
+
</source>
+
  
You will need the "jobId" later on to finish the job run. The job run Id can also be found via the monitoring API for the job:
+
<tt>
 
+
  GET http://localhost:8080/smila/jobmanager/jobs/indexUpdate/
<source lang="javascript">
+
</tt>
#Request
+
GET http://localhost:8080/smila/jobmanager/jobs/indexUpdate/
+
</source>
+
  
 
In the <tt>SMILA.log</tt> file you will see a message like that:
 
In the <tt>SMILA.log</tt> file you will see a message like that:
<pre>
+
<tt>
INFO ... internal.JobRunEngineImpl  - started job run '20110901-121343613053' for job 'indexUpdate'
+
  INFO ... internal.JobRunEngineImpl  - started job run '20110901-121343613053' for job 'indexUpdate'
</pre>
+
</tt>
  
'''Further information''': The "indexUpdate" workflow uses the [[SMILA/Documentation/Worker/PipelineProcessorWorker|PipelineProcessorWorker]] that executes the synchronous "AddPipeline" BPEL workflow. So, the synchronous "AddPipeline" BPEL workflow is embedded in the asynchronous "indexUpdate" workflow. For more details about the "indexUpdate" workflow and "indexUpdate" job definitions see <tt>SMILA/configuration/org.eclipse.smila.jobmanager/workflows.json</tt> and <tt>jobs.json</tt>). For more information about job management in general please check the [[SMILA/Documentation/JobManager|JobManager documentation]].
+
'''Further information''': The "indexUpdate" workflow uses the [[SMILA/Documentation/Worker/ScriptProcessorWorker|ScriptProcessorWorker]] that executes the JavaScript "add.js" workflow. So, the synchronous script call is embedded in the asynchronous "indexUpdate" workflow. For more details about the "indexUpdate" workflow and "indexUpdate" job definitions see <tt>SMILA/configuration/org.eclipse.smila.jobmanager/workflows.json</tt> and <tt>jobs.json</tt>). For more information about job management in general please check the [[SMILA/Documentation/JobManager|JobManager documentation]].
  
=== Start the crawler ===
+
=== Start the crawl job run  ===
  
Now that the indexing job is running we need to push some data to it. There is a predefined job for indexing the SMILA Eclipsepedia pages which we are going to start right now.  For more information about crawl jobs please see [[SMILA/Documentation/Importing/Concept|Importing Concept]]. For more information on jobs and tasks in general visit the [[SMILA/Documentation/JobManager|JobManager manual]].
+
Now that the indexing job is running we need to push some data to it. There is a predefined job for importing the [[SMILA|SMILA Wiki]] pages which we are going to start right now.   
 
+
<tt>
To start the job run, POST the following JSON fragment with your REST client to SMILA:
+
  POST http://localhost:8080/smila/jobmanager/jobs/crawlSmilaWiki/
<source lang="javascript">
+
</tt>
#Request
+
POST http://localhost:8080/smila/jobmanager/jobs/crawlSmilaWiki/
+
</source>
+
  
This starts the job <tt>crawlSmilaWiki</tt>, which crawls the [[SMILA|SMILA Eclipsepedia]] starting with <tt>http://wiki.eclipse.org/SMILA</tt> and (by applying the configured filters) following only links that have the same prefix. All pages crawled matching this prefix will be pushed to the import job.
+
This starts the job <tt>crawlSmilaWiki</tt>, which crawls the SMILA Wiki starting with <tt>http://wiki.eclipse.org/SMILA</tt> and (by applying the configured filters) following only links that have the same prefix. All pages crawled matching this prefix will be pushed to the import job.
  
If you like, you can monitor both job runs with your REST client at the following URIs:
+
Both job runs can be monitored via SMILA's REST API:
 +
* All jobs: [http://localhost:8080/smila/jobmanager/jobs/ http://localhost:8080/smila/jobmanager/jobs/]
 
* Crawl job: [http://localhost:8080/smila/jobmanager/jobs/crawlSmilaWiki http://localhost:8080/smila/jobmanager/jobs/crawlSmilaWiki]
 
* Crawl job: [http://localhost:8080/smila/jobmanager/jobs/crawlSmilaWiki http://localhost:8080/smila/jobmanager/jobs/crawlSmilaWiki]
 
* Import job: [http://localhost:8080/smila/jobmanager/jobs/indexUpdate http://localhost:8080/smila/jobmanager/jobs/indexUpdate]
 
* Import job: [http://localhost:8080/smila/jobmanager/jobs/indexUpdate http://localhost:8080/smila/jobmanager/jobs/indexUpdate]
Or both in one overview at
 
* [http://localhost:8080/smila/jobmanager/jobs/ http://localhost:8080/smila/jobmanager/jobs/]
 
  
The crawling of the wikipedia page should take some time. If all pages are processed, the status of the [http://localhost:8080/smila/jobmanager/jobs/crawlSmilaWiki crawlSmilaWiki]'s job run will change to {{code|SUCCEEDED}}. You can have a look at SMILA's search page to find out if some of the pages have already made their way into the Solr index.
+
The crawling of the SMILA Wiki pages should take some time. If all pages are processed, the status of the [http://localhost:8080/smila/jobmanager/jobs/crawlSmilaWiki crawlSmilaWiki]'s job run will change to {{code|SUCCEEDED}}. You can continue with the SMILA search (next chapter) to find out if some of the pages have already made their way into the Solr index.
  
'''Further information:''' You can find details about the relevant [[SMILA/Manual#Importing|Import concepts here]].
+
'''Further information:''' For more information about importing and crawl jobs please see [[SMILA/Documentation#Importing | SMILA Importing ]]. For more information on jobs and tasks in general visit the [[SMILA/Documentation/JobManager|JobManager manual]].
  
 
== Search the index ==
 
== Search the index ==
  
{{note|Since SMILA uses [[SMILA/Documentation/Solr#solrconfig.xml|Solr's autocommit feature]] (which is configured in <tt>solrconfig.xml</tt> to a period of 60 seconds or 1000 documents, whichever comes first) it might take some time until you retrieve results.}}
+
{{note|Since SMILA uses [[SMILA/Documentation/Solr#solrconfig.xml|Solr's autocommit feature]] (which is configured in <tt>solrconfig.xml</tt> to a period of 30 seconds or 1000 documents, whichever comes first) it might take some time until you retrieve results.}}
  
To search the index which was created by the crawlers, point your browser to <tt>http://localhost:8080/SMILA/search</tt>. There are currently two stylesheets from which you can select by clicking the respective links in the upper left corner of the header bar: The ''Default'' stylesheet shows a reduced search form with text fields like ''Query'', ''Result Size'', and ''Index'', adequate to query the full-text content of the indexed documents. The ''Advanced'' stylesheet in turn provides a more detailed search form with text fields for meta-data search like for example ''Path'', ''MimeType'', ''Filename'', and other document attributes.  
+
To search the created index, point your browser to <tt>http://localhost:8080/SMILA/search</tt>.  
 +
 
 +
There are currently two stylesheets from which you can select by clicking the respective links in the upper left corner of the header bar: The ''Default'' stylesheet shows a reduced search form with text fields like ''Query'', ''Result Size'', and ''Index'', adequate to query the full-text content of the indexed documents. The ''Advanced'' stylesheet in turn provides a more detailed search form with text fields for meta-data search like for example ''Path'', ''MimeType'', ''Filename'', and other document attributes.  
  
 
'''To use the ''Default'' Stylesheet''':
 
'''To use the ''Default'' Stylesheet''':
 
#Point your browser to <tt>http://localhost:8080/SMILA/search</tt>.
 
#Point your browser to <tt>http://localhost:8080/SMILA/search</tt>.
#Enter a word that you expect to be contained in your dummy files into the ''Query'' text field.
+
#Enter the search term(s) into the ''Query'' text field (e.g. "SMILA").
 
# Click ''OK'' to send your query to SMILA.  
 
# Click ''OK'' to send your query to SMILA.  
  
Line 167: Line 151:
  
 
Although there's no need for it, we can finish our previously started indexing job run via REST client now:
 
Although there's no need for it, we can finish our previously started indexing job run via REST client now:
(replace <job-id> with the job-id you got before when [[#Start_indexing_job_run|you started the job run]]).
+
(replace <job-id> with the job run id you got before when [[#Start_indexing_job_run|you started the job run]]).
  
<source lang="javascript">
+
<tt>
#Request
+
  POST http://localhost:8080/smila/jobmanager/jobs/indexUpdate/<job-id>/finish   
POST http://localhost:8080/smila/jobmanager/jobs/indexUpdate/<job-id>/finish   
+
</tt>
</source>
+
  
 
You can monitor the job run via your browser to see that it has finished successfully:
 
You can monitor the job run via your browser to see that it has finished successfully:
<source lang="javascript">
+
<tt>
#Request
+
  GET http://localhost:8080/smila/jobmanager/jobs/indexUpdate/<job-id>
GET http://localhost:8080/smila/jobmanager/jobs/indexUpdate/<job-id>
+
</tt>
</source>
+
  
 
In the <tt>SMILA.log</tt> file you will see messages like this:
 
In the <tt>SMILA.log</tt> file you will see messages like this:
<pre>
+
<tt>
 
  INFO ... internal.JobRunEngineImpl  - finish called for job 'indexUpdate', run '20110901-141457584011'
 
  INFO ... internal.JobRunEngineImpl  - finish called for job 'indexUpdate', run '20110901-141457584011'
 
  ...
 
  ...
 
  INFO ... internal.JobRunEngineImpl  - Completing job run '20110901-141457584011' for job 'indexUpdate' with final state SUCCEEDED
 
  INFO ... internal.JobRunEngineImpl  - Completing job run '20110901-141457584011' for job 'indexUpdate' with final state SUCCEEDED
</pre>
+
</tt>
 +
 
 +
<br/>
 +
<br/>
 +
'''Congratulations, you've just finished the tutorial! '''
  
Congratulations, you've just crawled the SMILA Eclipsepedia, indexed the pages and searched through them. For more, just visit [[SMILA/Manual|SMILA Manual]].
+
You crawled the SMILA Wiki, indexed the pages and searched through them. For more, just continue with the chapter below or visit the [[SMILA/Documentation|SMILA Documentation]].
  
 
== Further steps ==
 
== Further steps ==
Line 193: Line 179:
 
=== Crawl the filesystem ===
 
=== Crawl the filesystem ===
  
SMILA has also a predefined job to crawl the file system ("crawlFilesystem"), but you will have to either adapt the predefined job to point it to a valid folder in your filesystem or create your own job.
+
SMILA has also a predefined job to crawl the file system ("crawlFilesystem"), but you will have to either adapt the predefined job to point it to a valid folder in your filesystem or create your own job.  
  
 
We will settle for the second option, because it does not need that you stop and restart SMILA.
 
We will settle for the second option, because it does not need that you stop and restart SMILA.
  
 
==== Create your Job ====
 
==== Create your Job ====
POST the following job description to [[SMILA/Documentation/JobDefinitions#List.2C_create.2C_modify_jobs|SMILA's Job API]] at <tt>http://localhost:8080/smila/jobmanager/jobs</tt>. Adapt the <tt>rootFolder</tt> parameter to point to an existing folder on your machine where you have placed some files (e.g. plain text, HTML files). If your path includes backslashes, escape them with an additional backslash, e.g. <tt>c:\\data\files</tt>.
+
POST the following job description to [[SMILA/Documentation/JobDefinitions#List.2C_create.2C_modify_jobs|SMILA's Job API]]. Adapt the <tt>rootFolder</tt> parameter to point to an existing folder on your machine where you have placed some files (e.g. plain text, office docs or HTML files). If your path includes backslashes, escape them with an additional backslash, e.g. <tt>c:\\data\\files</tt>.
<source lang="javascript">
+
<tt>
#Request
+
POST http://localhost:8080/smila/jobmanager/jobs/
POST http://localhost:8080/smila/jobmanager/jobs/
+
{
{
+
 
   "name":"crawlFilesAtData",
 
   "name":"crawlFilesAtData",
 
   "workflow":"fileCrawling",
 
   "workflow":"fileCrawling",
Line 216: Line 201:
 
       "fileExtension":"Extension",
 
       "fileExtension":"Extension",
 
       "fileLastModified":"LastModifiedDate"
 
       "fileLastModified":"LastModifiedDate"
    }
+
      }
  }
+
  }
}
+
}
</source>
+
</tt>
  
For text files other than plain text and HTML you cannot search inside the document's text (at least not right now, but you might have a look at [[SMILA/Documentation/AperturePipelet|Aperture Pipelet]] which addresses this problem).
+
''Hint: Not all file formats are supported by SMILA out-of-the-box. Have a look [[SMILA/Documentation/TikaPipelet#Supported_document_types | here]] for details.''
  
 
==== Start your jobs ====
 
==== Start your jobs ====
  
*Start the <tt>indexUpdate</tt> (see [[#Start_indexing_job_run|Start indexing job run]]), if you have already stopped it. If it is still running, that's fine:
+
* Start the <tt>indexUpdate</tt> job (see [[#Start_indexing_job_run|Start indexing job run]]), if you have already stopped it. (If it is still running, that's fine)
<div style="margin-left: 1.5em;">
+
<tt>
<source lang="javascript">
+
  POST http://localhost:8080/smila/jobmanager/jobs/indexUpdate/
#Request
+
</tt>
POST http://localhost:8080/smila/jobmanager/jobs/indexUpdate/
+
 
</source>
+
* Start your <tt>crawlFilesAtData</tt> job. This new job behaves just like the web crawling job we used above, but its run time might be shorter, depending on how much data actually is at your {{code|rootFolder}}.
</div>
+
<tt>
*Start your <tt>crawlFilesAtData</tt> job similar to [[#Start_the_crawler|Start the crawler]] but now use the job name <tt>crawlFilesAtData</tt> instead of <tt>crawlSmilaWiki</tt>. This new job behaves just like the web crawling job, but its run time might be shorter, depending on how much data actually is at your {{code|rootFolder}}.
+
  POST http://localhost:8080/smila/jobmanager/jobs/crawlFilesAtData/
<div style="margin-left: 1.5em;">
+
</tt>
<source lang="javascript">
+
#Request
+
POST http://localhost:8080/smila/jobmanager/jobs/crawlFilesAtData/
+
</source>
+
</div>
+
  
 
==== Search for your new data ====
 
==== Search for your new data ====
#After the job run's finished, wait a bit, then check whether the data has been indexed (see [[#Search_the_index|Search the index]] for help).
+
#After the job run's finished, wait a bit, then check whether the data has been indexed (see [[#Search_the_index|Search the index]]).
 
#It is also a good idea to check the log file for errors.
 
#It is also a good idea to check the log file for errors.
  
 
=== 5 more minutes to change the workflow ===
 
=== 5 more minutes to change the workflow ===
  
The [[SMILA/Documentation/5 more minutes to change the workflow|5 more minutes to change the workflow]] show how you can configure the system so that data from different data sources will go through different workflows and pipelines and will be indexed into different indices.
+
The [[SMILA/Documentation/5 more minutes to change the workflow|5 more minutes to change the workflow]] show how you can configure the system so that data from different data sources will go through different workflows and scripts and will be indexed into different indices.
(see [[#Start_indexing_job_run|Start indexing job run]]), if you have already stopped it. If it is still running, that's fine:
+

Latest revision as of 06:21, 3 November 2014


On this page we describe the necessary steps to install and run SMILA in order to create a search index on the SMILA Eclipsepedia pages and search them.

If you have any troubles or the results differ from what is described here, check the FAQ.

Supported Platforms

The following platforms are supported:

  • Linux 32 Bit
  • Linux 64 Bit
  • Mac OS X 64 Bit (Cocoa)
  • Windows 32 Bit
  • Windows 64 Bit

Download and start SMILA

Download the SMILA package matching your operation system and unpack it to an arbitrary folder. This will result in the following folder structure:

/<SMILA>
  /configuration    
  ...
  SMILA
  SMILA.ini

Preconditions

To be able to start SMILA, check the following preconditions first:

JRE

You will have to provide a JRE executable to be able to run SMILA. The JVM version should be Java 7 (or newer). You may either:

  • add the path of your local JRE executable to the PATH environment variable
    or
  • add the argument -vm <path/to/jre/executable> right at the top of the file SMILA.ini.
    Make sure that -vm is indeed the first argument in the file, that there is a line break after it and that there are no leading or trailing blanks. It should look similar to the following:
-vm
d:/java/jre7/bin/java
...

Linux

When using Linux, make sure that the file SMILA has executable permissions. If not, set the permission by running the following commands in a console:

chmod +x ./SMILA

MacOS

When using MAC, switch to SMILA.app/Contents/MacOS/ and set the permission by running the following command in a console:

chmod a+x ./SMILA

Start SMILA

To start SMILA, simply start the SMILA executable.

You can see that SMILA has fully started if the following line is printed on the OSGI console:

 ...
 HTTP server started successfully on port 8080

and you can access SMILA's REST API at http://localhost:8080/smila/.

If it doesn't work, check the log file (SMILA.log) for possible errors.

Stop SMILA

To stop SMILA, type close into the OSGI console and press Enter:

 osgi> close

Start Indexing Job and Crawl Import

Now we're going to crawl and process the SMILA Eclipsepedia pages, Finally we index and search them by using the embedded Solr integration.

Install a REST client

We're going to use SMILA's REST API to start and stop jobs, so you need a REST client. In REST Tools you find a selection of recommended browser plugins if you haven't got a suitable REST client yet.

Start the indexing job run

We are going to start the predefined indexing job "indexUpdate" based on the predefined asynchronous workflow with the same name. This indexing job will process the imported data.

Use your favorite REST Client to start a job run for the job "indexUpdate":

 POST http://localhost:8080/smila/jobmanager/jobs/indexUpdate/

Your REST client will show a result like this:

{
  "jobId" : "20110901-121343613053",
  "url" : "http://localhost:8080/smila/jobmanager/jobs/indexUpdate/20110901-121343613053/"
}

You will need the job run id ("jobId") later on to finish the job run. The job run Id can also be found via the monitoring API for the job:

 GET http://localhost:8080/smila/jobmanager/jobs/indexUpdate/

In the SMILA.log file you will see a message like that:

 INFO ... internal.JobRunEngineImpl   - started job run '20110901-121343613053' for job 'indexUpdate'

Further information: The "indexUpdate" workflow uses the ScriptProcessorWorker that executes the JavaScript "add.js" workflow. So, the synchronous script call is embedded in the asynchronous "indexUpdate" workflow. For more details about the "indexUpdate" workflow and "indexUpdate" job definitions see SMILA/configuration/org.eclipse.smila.jobmanager/workflows.json and jobs.json). For more information about job management in general please check the JobManager documentation.

Start the crawl job run

Now that the indexing job is running we need to push some data to it. There is a predefined job for importing the SMILA Wiki pages which we are going to start right now.

 POST http://localhost:8080/smila/jobmanager/jobs/crawlSmilaWiki/

This starts the job crawlSmilaWiki, which crawls the SMILA Wiki starting with http://wiki.eclipse.org/SMILA and (by applying the configured filters) following only links that have the same prefix. All pages crawled matching this prefix will be pushed to the import job.

Both job runs can be monitored via SMILA's REST API:

The crawling of the SMILA Wiki pages should take some time. If all pages are processed, the status of the crawlSmilaWiki's job run will change to SUCCEEDED. You can continue with the SMILA search (next chapter) to find out if some of the pages have already made their way into the Solr index.

Further information: For more information about importing and crawl jobs please see SMILA Importing . For more information on jobs and tasks in general visit the JobManager manual.

Search the index

Note.png
Since SMILA uses Solr's autocommit feature (which is configured in solrconfig.xml to a period of 30 seconds or 1000 documents, whichever comes first) it might take some time until you retrieve results.


To search the created index, point your browser to http://localhost:8080/SMILA/search.

There are currently two stylesheets from which you can select by clicking the respective links in the upper left corner of the header bar: The Default stylesheet shows a reduced search form with text fields like Query, Result Size, and Index, adequate to query the full-text content of the indexed documents. The Advanced stylesheet in turn provides a more detailed search form with text fields for meta-data search like for example Path, MimeType, Filename, and other document attributes.

To use the Default Stylesheet:

  1. Point your browser to http://localhost:8080/SMILA/search.
  2. Enter the search term(s) into the Query text field (e.g. "SMILA").
  3. Click OK to send your query to SMILA.

To use the Advanced Stylesheet:

  1. Point your browser to http://localhost:8080/SMILA/search.
  2. Click Advanced to switch to the detailed search form.
  3. For example, to find a file by its name, enter the file name into the Filename text field, then click OK to submit your search.

Stop indexing job run

Although there's no need for it, we can finish our previously started indexing job run via REST client now: (replace <job-id> with the job run id you got before when you started the job run).

 POST http://localhost:8080/smila/jobmanager/jobs/indexUpdate/<job-id>/finish  

You can monitor the job run via your browser to see that it has finished successfully:

 GET http://localhost:8080/smila/jobmanager/jobs/indexUpdate/<job-id>

In the SMILA.log file you will see messages like this:

INFO ... internal.JobRunEngineImpl   - finish called for job 'indexUpdate', run '20110901-141457584011'
...
INFO ... internal.JobRunEngineImpl   - Completing job run '20110901-141457584011' for job 'indexUpdate' with final state SUCCEEDED



Congratulations, you've just finished the tutorial!

You crawled the SMILA Wiki, indexed the pages and searched through them. For more, just continue with the chapter below or visit the SMILA Documentation.

Further steps

Crawl the filesystem

SMILA has also a predefined job to crawl the file system ("crawlFilesystem"), but you will have to either adapt the predefined job to point it to a valid folder in your filesystem or create your own job.

We will settle for the second option, because it does not need that you stop and restart SMILA.

Create your Job

POST the following job description to SMILA's Job API. Adapt the rootFolder parameter to point to an existing folder on your machine where you have placed some files (e.g. plain text, office docs or HTML files). If your path includes backslashes, escape them with an additional backslash, e.g. c:\\data\\files.

POST http://localhost:8080/smila/jobmanager/jobs/
{
 "name":"crawlFilesAtData",
 "workflow":"fileCrawling",
 "parameters":{
   "tempStore":"temp",
   "dataSource":"file",
   "rootFolder":"/data",
   "jobToPushTo":"indexUpdate",
   "mapping":{
     "fileContent":"Content",
     "filePath":"Path",       
     "fileName":"Filename",       
     "fileExtension":"Extension",
     "fileLastModified":"LastModifiedDate"
     }
  }
}

Hint: Not all file formats are supported by SMILA out-of-the-box. Have a look here for details.

Start your jobs

  • Start the indexUpdate job (see Start indexing job run), if you have already stopped it. (If it is still running, that's fine)

  POST http://localhost:8080/smila/jobmanager/jobs/indexUpdate/

  • Start your crawlFilesAtData job. This new job behaves just like the web crawling job we used above, but its run time might be shorter, depending on how much data actually is at your rootFolder.

 POST http://localhost:8080/smila/jobmanager/jobs/crawlFilesAtData/

Search for your new data

  1. After the job run's finished, wait a bit, then check whether the data has been indexed (see Search the index).
  2. It is also a good idea to check the log file for errors.

5 more minutes to change the workflow

The 5 more minutes to change the workflow show how you can configure the system so that data from different data sources will go through different workflows and scripts and will be indexed into different indices.