The backend needs some basic configuration to configure data sources that should be crawled.
Configure data sources
- For configuration, make sure that the backend's WAR-archive is installed and unpacked in your application server (see Integrated Search/Installation)
- You should then be able to find a directory called
- In here, you find (among other) two configuration files, which you need to edit:
repo_config.xml contains access data for the repositories you want to crawl (see repo_config.xml for details)
crawl_config.xml helps you to group the repositories into "crawls" (see crawl_config.xml for details)
Crawl data sources
- Now that you configured everything, you might want to start your first crawl to fill the index with real that.
- Navigate in the new
teamweaverIS-backend folder and execute
cc.sh. This will generate some scripts required for crawling.
- Execute the crawl shell script (
crawl.sh with the Id of the crawl you want to execute (as defined in crawl_config.xml) - e.g. "
- Note 1: Crawling is incremental. So when you start the same crawl later again, it will only update new/changed/deleted files.
- Note 2: TeamWeaver does not provide means for automatically launching crawls. You need to schedule a task on your server machine which executes the crawl regularly (e.g. once a night) to keep the index up-to-date.
Configuring "push" indexing
Besides having the backend crawling the data sources as described above, the backend also allows data sources to proactively "push" new or changed data to the index. This makes the index more "fresh", but would typically require modifications on the side of the crawled data source. Therefore, "push" indexing is currently only supported for Polarion and for MediaWiki.
Push-indexing needs to be configured in the backend as well as in the data source system. In the backend, you need to enabled pushIndexing, define an Id and provide a
pushIndexAuthKey (see repo_config.xml).
For configuring the data source system, you need the following information:
The actual way of configuration should be described in the documentation. See e.g. Woogle4MediaWiki/Configuration.