TeamWeaverWiki - User contributions [en]

Sandbox DataImport ActualWeather

2010-05-27T13:45:23Z

ChristianRoehr: Created page with '{{#ws:ActualWeather | location = Karlsruhe, Germany | ?result.maxTemperatureC | _format=list }}'

{{#ws:ActualWeather
| location = Karlsruhe, Germany
| ?result.maxTemperatureC
| _format=list
}}

WebService:ActualWeather

2010-05-27T13:44:27Z

ChristianRoehr: Created page with '<WebService> <uri name="http://api.wunderground.com/auto/wui/geo/ForecastXML/index.xml" /> <protocol>REST</protocol> <method name="get" /> <parameter name="location" optional="t…'

Woogle4MediaWiki/Feedback

2010-05-21T12:45:20Z

ChristianRoehr: /* Please describe as precisely as possible */

The Woogle team appreciates feedback that helps to improve Woogle and guide its future development. This page conveys some information to make the feedback process more enjoyable for you as a user and for us developers.

== How to send us your suggestions and error reports ==
We would like you to use our end-user issue tracking system, running at http://octopus13.fzi.de:8080/browse/WMW. Do not worry, when using this simple form-based interface, submitting feedback is just as simple as sending an E-Mail.

However, if you actually prefer sending as an E-Mail, please feel free to do so via [[File:Email.png]]. Alternatively, you may consider using the discussion tab of this Wiki page (you will need to create an account for this Wiki before).

== How to best report problems and errors ==
Before sending us your problem, make sure you checked the [[Woogle4MediaWiki/Admin manual|admin manual]] and the [[Woogle4MediaWiki/FAQ|FAQ]] (and probably even our development issue tracker), if the problem has been reported/recognized before.

If you want to help us unterstand and fix your errors, you can follow some simple guidelines (also see the instructions at [[Integrated Search/Feedback]] if you run WoogleRemote with an Integrated Search backend, and think your problem is related to that):

=== Please describe as precisely as possible ===
* The exact action you were pursuing before the problem occured
* The behaviour you would have expected from the system
* The (problematic) behaviour that actually occured
* If feasible, provide some screenshots of the problem (if your are using Firefox, there is a [http://pearlcrescent.com/products/pagesaver/ nice plugin])

=== Please provide us with some context information about your system setup ===
* Operating System, PHP Version, MediaWiki version, Woogle version
* Most of this information is contained in the following files/screenshots, that might be helpful for us to investigate your case:
** A screen copy or HTML dump of the Special:WoogleConfig page in your Wiki
** A screen copy or HTML dump of the Special:Version page in your Wiki
** A copy of your MediaWiki LocalSettings.php file
** A zip file containing the log files located in \MediaWiki\extensions\Woogle\logs
* To find out details about your PHP environment (installed modules etc.) the easiest way is to create and subsequently open a file <code>info.php</code> in your webserver root directory with the following content:
<pre>
<?php
phpinfo();
?>
</pre>

__NOTOC__

Woogle4MediaWiki/Feedback

2010-05-21T12:42:47Z

ChristianRoehr: /* How to send us your suggestions and error reports */

The Woogle team appreciates feedback that helps to improve Woogle and guide its future development. This page conveys some information to make the feedback process more enjoyable for you as a user and for us developers.

== How to send us your suggestions and error reports ==
We would like you to use our end-user issue tracking system, running at http://octopus13.fzi.de:8080/browse/WMW. Do not worry, when using this simple form-based interface, submitting feedback is just as simple as sending an E-Mail.

However, if you actually prefer sending as an E-Mail, please feel free to do so via [[File:Email.png]]. Alternatively, you may consider using the discussion tab of this Wiki page (you will need to create an account for this Wiki before).

== How to best report problems and errors ==
Before sending us your problem, make sure you checked the [[Woogle4MediaWiki/Admin manual|admin manual]] and the [[Woogle4MediaWiki/FAQ|FAQ]] (and probably even our development issue tracker), if the problem has been reported/recognized before.

If you want to help us unterstand and fix your errors, you can follow some simple guidelines (also see the instructions at [[Integrated Search/Feedback]] if you run WoogleRemote with an Integrated Search backend, and think your problem is related to that):

=== Please describe as precisely as possible ===
* The exact action you were pursuing before the problem occured
* The behaviour you would have expected from the system
* The (problematic) behaviour that actually occured
* If feasible, provide some screenshots the problem (if your are using Firefox, there is a [http://pearlcrescent.com/products/pagesaver/ nice plugin])

=== Please provide us with some context information about your system setup ===
* Operating System, PHP Version, MediaWiki version, Woogle version
* Most of this information is contained in the following files/screenshots, that might be helpful for us to investigate your case:
** A screen copy or HTML dump of the Special:WoogleConfig page in your Wiki
** A screen copy or HTML dump of the Special:Version page in your Wiki
** A copy of your MediaWiki LocalSettings.php file
** A zip file containing the log files located in \MediaWiki\extensions\Woogle\logs
* To find out details about your PHP environment (installed modules etc.) the easiest way is to create and subsequently open a file <code>info.php</code> in your webserver root directory with the following content:
<pre>
<?php
phpinfo();
?>
</pre>

__NOTOC__

Sandbox GeSHi

2010-03-26T10:47:55Z

ChristianRoehr: Created page with '== <nowiki><source></nowiki> tag == <source lang="cpp"> #include <iostream> int main() { std::cout << "Hello, world!\n"; } </source> == <nowiki><syntaxhighlight></nowiki>…'

== <nowiki><source></nowiki> tag ==

<source lang="cpp">
#include <iostream>

int main()
{
std::cout << "Hello, world!\n";
}
</source>

== <nowiki><syntaxhighlight></nowiki> tag ==

This does not work, because we are using SyntaxHighlight_SeSHI r48711 (this was offered by mediawiki.org when choosing a proper version for MW 1.15.x), but [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi "Before rev:50696, the <nowiki><source></nowiki> tag was used."] instead of the <nowiki><syntaxhighlight></nowiki> tag.

<syntaxhighlight lang="cpp">
#include <iostream>

int main()
{
std::cout << "Hello, world!\n";
}
</syntaxhighlight>

Woogle4MediaWiki/Configuration

2010-01-18T08:41:04Z

ChristianRoehr: /* General configuration */

== English ==

=== General configuration ===
Open the file <code>[Your MediaWiki directory]/extensions/Woogle/WoogleConfig.php</code> and scroll down to the <code>WoogleConfig</code> class to configure Woogle. You can call <code>[MediaWiki URL]/Special:WoogleConfig</code> in your browser to see configured values at runtime.
<pre>
private static $config = array(
// edit values here // comment
// general configuration
'core' => array(true, 'enable or disable woogle at all'),
'replace' => array(true, 'replace built-in MediaWiki search'),
'advanced' => array(true, 'use Woogle "advanced" mode: redirection to an own wiki page for each search result'),
'advancedBox' => array(true, 'show the box for the "advanced" mode with the corresponding wiki content in it'),
'advancedWikiLink' => array(true, 'show a button to create a wiki page with the same name as the search string'),
'advancedWatch' => array(true, 'show a button to watch a search result for changes in the corresponding wiki page'),
'advancedDiscussion' => array(true, 'show a button including a link on the result\'s discussion page'),
'advancedNamespaceGrab' => array(true, 'if the (usually) Woogle:Namespace should be grabbed and redirected to the nonAdvanced url if advanced is turned off'),
'redLinkInfo' => array(false, 'show meta-info popups next to red links'),
'limitAccessToGroups' => array(false, 'access limited to mediawiki groups specified in $groups'),
'groups' => array(array('fzi'), 'groups access is limited to if $limitAccessToGroups'),
'defaultCount' => array(10, 'default number of results shown per page'),
'helpPage' => array('Woogle', 'wiki-page shown as help page'),
'resultWidth' => array(650, 'pixel-width of the result list'),
'searchOptions' => array('source=mediawiki', 'additional search options when using the built-in mediawiki search'),
'timeout' => array(0, 'timeout if the QueryService is down (in seconds)'),
'clickTracking' => array(true, 'if clicks are being tracked'),
'indexAddon' => array('Native', 'addon used for the Woogle index'),
'indexRepository' => array(17, 'repository id this wiki should use in the index')
);
</pre>

See the documentation for each value on the right side. Typically, there is '''no need to change most of these values'''. Values that required consideration are:
* <code>indexAddon</code> - put in 'Native' or 'Remote' depending on your choice of the backend!
* <code>indexRepository</code> - put in a numeric id. For WoogleNative it is arbitrary, for WoogleRemote you need to use the repoId configured in the backend (c.f. [[repo_config.xml]])

NB: There is also the possibility to change Woogle settings in your LocalSettings.php, e.g.
WoogleConfig::set('indexAddon', 'Native');
or
WoogleConfig::set('indexAddon', 'Remote');
is the preferred way to chose the index addon, you want to use. Add these statements after the 'include woogle' command.

For WoogleRemote, you need to make additional settings (see below).

=== Specific settings for WoogleRemote ===
Edit <code>[Your MediaWiki directory]/extensions/Woogle/addons/Remote.php</code>.

<pre>
function woogleRemoteConfig(&$config) {
$config['remoteAuthKey'] = array("anonymous", 'authKey being passed to the remote Backend');
$config['remoteQueryServiceUrl'] = array('http://octopus13.fzi.de:9999/teamweaverIS-backend/services/phpQuery',
'remote query service url');
$config['remoteUpdateServiceUrl'] = array('http://octopus13.fzi.de:9999/teamweaverIS-backend/services/phpUpdate',
'remote update service url');
$config['remoteIndexServiceUrl'] = array('http://octopus13.fzi.de:9999/teamweaverIS-backend/services/phpIndex',
'remote update service url');
$config['remoteOptions'] = array(array('username' => 'waves', 'password' => 'trrwd'),
'options being passed to the HessianClient');
$config['remoteServiceName'] = array('Woogle', 'service name being passed to the wavesIS backend');
$config['remoteServiceVersion'] = array('0.99', 'service version being passed to the wavesIS backend');
$config['remotePushIndexAuthKey'] = array('dummyKey', 'key the push index is called with to authenticate');
return true;
}
</pre>

Values you need to configure:
* <code>remote...ServiceUrl</code> - set the respective backend URLs here
* <code>remotePushIndexAuthKey</code> - for indexing - as configured in the backend [[repo_config.xml]]
* <code>remoteAuthKey</code> - only required for querying, if the backend is set to securityEnabled = true;

== Deutsch (German) (nicht auf dem neuesten Stand) ==

=== Allgemeine Konfiguration ===

Die folgenden Einstellungen können in der Datei <code>[MediaWiki Installationverzeichnis]/extensions/Woogle/WoogleConfig.php</code> vorgenommen werden. Wenn Sie die Seite <code>[MediaWiki URL]/Special:WoogleConfig</code> in Ihrem Web-Broweser öffnen, können Sie die Konfigurationswerte zur Laufzeit sehen.
<pre>
private static $config = array(
// edit values here // comment
'advanced' => array(true, 'use Woogle "advanced" mode'),
'advancedBox' => array(true, 'show the box for the "advanced" mode with the corresponding wiki content in it'),
'advancedWikiLink' => array(true, 'show a button to create a wiki page with the same name as the search string'),
'advancedWatch' => array(true, 'show a button to watch a search result for changes in the corresponding wiki page'),
'advancedNamespaceGrab' => array(true, 'if the (usually) Woogle:Namespace should be grabbed and redirected to the nonAdvanced url if advanced is turned off'),
'limitAccessToGroups' => array(false, 'access limited to mediawiki groups specified in $groups'),
'groups' => array(array('fzi'), 'groups access is limited to if $limitAccessToGroups'),
'defaultCount' => array(10, 'default number of results shown per page'),
'helpPage' => array('Woogle', 'wiki-page shown as help page'),
'resultWidth' => array(650, 'pixel-width of the result list'),
'secure' => array(false, 'mediawiki being accessed with SSL'),
'searchOptions' => array('source=mediawiki', 'additional search options when using the built-in mediawiki search'),
'remoteQueryService' => array(false, 'query service remote or native - if set to false you can skip the rest of the configuration, but make sure to setup the native index with Special:WoogleNative'),
'authKey' => array("anonymous", 'authKey being passed to the remote Backend'),
'queryServiceUrl' => array('http://server:8080/teamweaverIS-backend/services/phpQuery',
'remote query service url, only relevant for the remote query service'),
'updateServiceUrl' => array('http://server:8080/teamweaverIS-backend/services/phpUpdate',
'remote update service url, only relevant for the remote query service'),
'indexServiceUrl' => array('http://server:8080/teamweaverIS-backend/services/phpIndex',
'remote update service url, only relevant for the remote query service'),
'options' => array(array('username' => 'waves', 'password' => 'trrwd'),
'options being passed to the HessianClient, only relevant for the remote query service'),
'clickTracking' => array(false, 'if clicks are being tracked, only relevant for the remote query service'),
'serviceName' => array('Woogle', 'service name being passed to the wavesIS backend, only relevant for the remote query service'),
'serviceVersion' => array('0.2 beta', 'service version being passed to the wavesIS backend, only relevant for the remote query service'),
);

* $groups: Array der erlaubten Mediawiki Benutzergruppen (wenn $limitAccessToGroups true ist)
* $limitAccessToGroups: limitiert den Zugriff auf die Woogle-Suche auf die Gruppen in $groups
* $clickTracking: ob click tracking aktiviert ist oder nicht
* $queryServiceUrl: die URL zum teamweaverIS Backend QueryService
* $updateServiceUrl: die URL zum teamweaverIS Backend UpdateService
* $options: Array mit Optionen fuer den Backend Service - z.B. wenn auf dem Tomcat die HTTP Authentifizierung aktiviert ist (Felder username und password)
* $serviceName: mit welchem Namen sich Woogle beim Backend authentifizieren soll
* $serviceVersion: mit welcher Version sich Woogle beim Backend authentifizieren soll
* $helpPage: auf welcher Wiki-Seite sich die Woogle-Hilfe befindet - gibt es keine einfach leer lassen
* $secure: ob Woogle hinter einer SSL-Verbindung ist
* $searchOptions: QueryString, der hinter Wikisuchen gehaengt wird (z.B. Parameter fuer die erweiterte Suche, sodass gleich nur in einer Quelle gesucht wird)

</pre>

=== Woogle über die MediaWiki Suchmaske aufrufen ===
* in der <code>[MediaWiki Installationverzeichnis]/index.php</code> folgende Zeile nach <code>require_once( './includes/WebStart.php' );</code> einfügen, falls die Woogle-Suche mit der Standard-Searchbox funktionieren soll:
** <code>WoogleConfig::initSearch();</code>

__NOTOC__

Woogle4MediaWiki/Configuration

2010-01-18T08:39:53Z

ChristianRoehr: /* General configuration */

== English ==

=== General configuration ===
Open the file <code>[Your MediaWiki directory]/extensions/Woogle/WoogleConfig.php</code> and scroll down to the <code>WoogleConfig</code> class to configure Woogle. You can call <code>[MediaWiki URL]/Special:WoogleConfig</code> in your browser to see configured values at runtime.
<pre>
private static $config = array(
// edit values here // comment
// general configuration
'core' => array(true, 'enable or disable woogle at all'),
'replace' => array(true, 'replace built-in MediaWiki search'),
'advanced' => array(true, 'use Woogle "advanced" mode: redirection to an own wiki page for each search result'),
'advancedBox' => array(true, 'show the box for the "advanced" mode with the corresponding wiki content in it'),
'advancedWikiLink' => array(true, 'show a button to create a wiki page with the same name as the search string'),
'advancedWatch' => array(true, 'show a button to watch a search result for changes in the corresponding wiki page'),
'advancedDiscussion' => array(true, 'show a button including a link on the result\'s discussion page'),
'advancedNamespaceGrab' => array(true, 'if the (usually) Woogle:Namespace should be grabbed and redirected to the nonAdvanced url if advanced is turned off'),
'redLinkInfo' => array(false, 'show meta-info popups next to red links'),
'limitAccessToGroups' => array(false, 'access limited to mediawiki groups specified in $groups'),
'groups' => array(array('fzi'), 'groups access is limited to if $limitAccessToGroups'),
'defaultCount' => array(10, 'default number of results shown per page'),
'helpPage' => array('Woogle', 'wiki-page shown as help page'),
'resultWidth' => array(650, 'pixel-width of the result list'),
'searchOptions' => array('source=mediawiki', 'additional search options when using the built-in mediawiki search'),
'timeout' => array(0, 'timeout if the QueryService is down (in seconds)'),
'clickTracking' => array(true, 'if clicks are being tracked'),
'indexAddon' => array('Native', 'addon used for the Woogle index'),
'indexRepository' => array(17, 'repository id this wiki should use in the index')
);
</pre>

See the documentation for each value on the right side. Typically, there is '''no need to change most of these values'''. Values that required consideration are:
* <code>indexAddon</code> - put in 'Native' or 'Remote' depending on your choice of the backend!
* <code>indexRepository</code> - put in a numeric id. For WoogleNative it is arbitrary, for WoogleRemote you need to use the repoId configured in the backend (c.f. [[repo_config.xml]])

NB: There is also the possibility to change Woogle settings in your LocalSettings.php, e.g.
WoogleConfig::set('indexAddon', 'Native');
or
WoogleConfig::set('indexAddon', 'Remote');
is the preferred way to chose the index addon, you want to use.

For WoogleRemote, you need to make additional settings (see below).

=== Specific settings for WoogleRemote ===
Edit <code>[Your MediaWiki directory]/extensions/Woogle/addons/Remote.php</code>.

<pre>
function woogleRemoteConfig(&$config) {
$config['remoteAuthKey'] = array("anonymous", 'authKey being passed to the remote Backend');
$config['remoteQueryServiceUrl'] = array('http://octopus13.fzi.de:9999/teamweaverIS-backend/services/phpQuery',
'remote query service url');
$config['remoteUpdateServiceUrl'] = array('http://octopus13.fzi.de:9999/teamweaverIS-backend/services/phpUpdate',
'remote update service url');
$config['remoteIndexServiceUrl'] = array('http://octopus13.fzi.de:9999/teamweaverIS-backend/services/phpIndex',
'remote update service url');
$config['remoteOptions'] = array(array('username' => 'waves', 'password' => 'trrwd'),
'options being passed to the HessianClient');
$config['remoteServiceName'] = array('Woogle', 'service name being passed to the wavesIS backend');
$config['remoteServiceVersion'] = array('0.99', 'service version being passed to the wavesIS backend');
$config['remotePushIndexAuthKey'] = array('dummyKey', 'key the push index is called with to authenticate');
return true;
}
</pre>

Values you need to configure:
* <code>remote...ServiceUrl</code> - set the respective backend URLs here
* <code>remotePushIndexAuthKey</code> - for indexing - as configured in the backend [[repo_config.xml]]
* <code>remoteAuthKey</code> - only required for querying, if the backend is set to securityEnabled = true;

== Deutsch (German) (nicht auf dem neuesten Stand) ==

=== Allgemeine Konfiguration ===

Die folgenden Einstellungen können in der Datei <code>[MediaWiki Installationverzeichnis]/extensions/Woogle/WoogleConfig.php</code> vorgenommen werden. Wenn Sie die Seite <code>[MediaWiki URL]/Special:WoogleConfig</code> in Ihrem Web-Broweser öffnen, können Sie die Konfigurationswerte zur Laufzeit sehen.
<pre>
private static $config = array(
// edit values here // comment
'advanced' => array(true, 'use Woogle "advanced" mode'),
'advancedBox' => array(true, 'show the box for the "advanced" mode with the corresponding wiki content in it'),
'advancedWikiLink' => array(true, 'show a button to create a wiki page with the same name as the search string'),
'advancedWatch' => array(true, 'show a button to watch a search result for changes in the corresponding wiki page'),
'advancedNamespaceGrab' => array(true, 'if the (usually) Woogle:Namespace should be grabbed and redirected to the nonAdvanced url if advanced is turned off'),
'limitAccessToGroups' => array(false, 'access limited to mediawiki groups specified in $groups'),
'groups' => array(array('fzi'), 'groups access is limited to if $limitAccessToGroups'),
'defaultCount' => array(10, 'default number of results shown per page'),
'helpPage' => array('Woogle', 'wiki-page shown as help page'),
'resultWidth' => array(650, 'pixel-width of the result list'),
'secure' => array(false, 'mediawiki being accessed with SSL'),
'searchOptions' => array('source=mediawiki', 'additional search options when using the built-in mediawiki search'),
'remoteQueryService' => array(false, 'query service remote or native - if set to false you can skip the rest of the configuration, but make sure to setup the native index with Special:WoogleNative'),
'authKey' => array("anonymous", 'authKey being passed to the remote Backend'),
'queryServiceUrl' => array('http://server:8080/teamweaverIS-backend/services/phpQuery',
'remote query service url, only relevant for the remote query service'),
'updateServiceUrl' => array('http://server:8080/teamweaverIS-backend/services/phpUpdate',
'remote update service url, only relevant for the remote query service'),
'indexServiceUrl' => array('http://server:8080/teamweaverIS-backend/services/phpIndex',
'remote update service url, only relevant for the remote query service'),
'options' => array(array('username' => 'waves', 'password' => 'trrwd'),
'options being passed to the HessianClient, only relevant for the remote query service'),
'clickTracking' => array(false, 'if clicks are being tracked, only relevant for the remote query service'),
'serviceName' => array('Woogle', 'service name being passed to the wavesIS backend, only relevant for the remote query service'),
'serviceVersion' => array('0.2 beta', 'service version being passed to the wavesIS backend, only relevant for the remote query service'),
);

* $groups: Array der erlaubten Mediawiki Benutzergruppen (wenn $limitAccessToGroups true ist)
* $limitAccessToGroups: limitiert den Zugriff auf die Woogle-Suche auf die Gruppen in $groups
* $clickTracking: ob click tracking aktiviert ist oder nicht
* $queryServiceUrl: die URL zum teamweaverIS Backend QueryService
* $updateServiceUrl: die URL zum teamweaverIS Backend UpdateService
* $options: Array mit Optionen fuer den Backend Service - z.B. wenn auf dem Tomcat die HTTP Authentifizierung aktiviert ist (Felder username und password)
* $serviceName: mit welchem Namen sich Woogle beim Backend authentifizieren soll
* $serviceVersion: mit welcher Version sich Woogle beim Backend authentifizieren soll
* $helpPage: auf welcher Wiki-Seite sich die Woogle-Hilfe befindet - gibt es keine einfach leer lassen
* $secure: ob Woogle hinter einer SSL-Verbindung ist
* $searchOptions: QueryString, der hinter Wikisuchen gehaengt wird (z.B. Parameter fuer die erweiterte Suche, sodass gleich nur in einer Quelle gesucht wird)

</pre>

=== Woogle über die MediaWiki Suchmaske aufrufen ===
* in der <code>[MediaWiki Installationverzeichnis]/index.php</code> folgende Zeile nach <code>require_once( './includes/WebStart.php' );</code> einfügen, falls die Woogle-Suche mit der Standard-Searchbox funktionieren soll:
** <code>WoogleConfig::initSearch();</code>

__NOTOC__

Sandbox

2009-07-29T07:48:22Z

ChristianRoehr:

[[Sandkasten]]

noch ein Sandkasten

noch mehr sand

Sandbox

2009-07-29T07:46:20Z

ChristianRoehr:

[[Sandkasten]]

noch ein Sandkasten

Woogle4MediaWiki/Installation

2009-07-15T15:43:30Z

ChristianRoehr: /* Installation steps */

== English ==
Before starting, it is important to understand that Woogle4MediaWiki can be run in '''two different modes''':
* WoogleNative - which is purely PHP-based - you can only search and index your Wiki as such, but no data outside the Wiki
* WoogleRemote - which connects to an [[Integrated Search]] backend - you can search any kind of data indexed by the backend (including e.g. file systems, SVN ressources etc.)

=== Prerequisites ===
* Woogle4MediaWiki requires [http://www.mediawiki.org/wiki/MediaWiki MediaWiki] in a version >= 1.11.0 (see also [[Woogle4MediaWiki/Compability|compatibility notes]])
* For WoogleNative (see above) you need
** A database user with CREATE TABLE privileges (or the database root account)
* For WoogleRemote you need
** An installed [[Integrated Search]] backend, and some configuration data (backend URL, repoId, pushIndexAuthKey; c.f. [[Integrated_Search/Configuration#Configuring_.22push.22_indexing|for push indexing]])

=== Installation steps ===
* Extract the content of the Woogle distribution ZIP-file to <code>[Your MediaWiki directory]/extensions/Woogle</code>
* Grant write permissions for the executing user on <code>[Your MediaWiki directory]/extensions/Woogle/addons/Native/index</code>, if you're using the Native addon
* At the end of the file <code>[Your MediaWiki directory]/LocalSettings.php</code> add the following line: <code>include_once('extensions/Woogle/Woogle.php' ); </code>
* [[Woogle4MediaWiki/Configuration|Configure]] everything
* Open <code>[MediaWiki URL]/index.php/Special:WoogleConfig</code> in your browser and click "index" to create an initial index
* Enter <code>[MediaWiki URL]/index.php/Special:Woogle</code> to your browser to check if everything works

== Deutsch (German) (nicht auf dem neuesten Stand) ==
* Den Inhalt der Woogle ZIP-Datei nach <code>[MediaWiki Installationverzeichnis]/extensions/Woogle</code> entpacken
* Dem ausführenden Benutzer Schreibrechte in <code>[MediaWiki Installationverzeichnis]/extensions/Woogle/addons/Native/index</code> gewähren, sofern das Native Addon benutzt wird
* Am Ende der Datei <code>[MediaWiki Installationverzeichnis]/LocalSettings.php</code> folgende Zeile einfügen:
** <code>include_once('extensions/Woogle/Woogle.php' ); </code>
* [[Woogle4MediaWiki/Configuration|Konfigurieren]] Sie Woogle
* Öffnen Sie die URL <code>[MediaWiki URL]/Special:WoogleConfig</code> und clicken Sie "index" um den Inhalt des Wikis initial zu indexieren
* Öffnen Sie die URL <code>[MediaWiki URL]/index.php/Special:Woogle</code> in Ihrem Web-Browser um zu sehen, ob die Installation funktioniert hat

Sandbox

2009-07-08T16:55:45Z

ChristianRoehr: Created page with 'Sandkasten'

[[Sandkasten]]

Contact

2009-06-24T06:47:57Z

ChristianRoehr: Created page with 'teamweaver.org is maintained by FZI Forschungszentrum Informatik an der Universität Karlsruhe (TH) in Germany (General contact data: http://www.fzi.de/eng/contactform.html). Fo…'

teamweaver.org is maintained by FZI Forschungszentrum Informatik an der Universität Karlsruhe (TH) in Germany (General contact data: http://www.fzi.de/eng/contactform.html).

For specific inquiries please contact [http://www.fzi.de/ipe/eng/mitarbeiter.php?id=418 Hans-Joerg Happel].

Woogle4MediaWiki/Configuration

2009-06-17T09:34:38Z

ChristianRoehr: Created page with '== English == === General configuration === Open the file <code>[Your MediaWiki directory]/extensions/Woogle/WoogleConfig.php</code> and scroll down to the <code>WoogleConfig</c…'

== English ==

=== General configuration ===
Open the file <code>[Your MediaWiki directory]/extensions/Woogle/WoogleConfig.php</code> and scroll down to the <code>WoogleConfig</code> class to configure Woogle. You can call <code>[MediaWiki URL]/Special:WoogleConfig</code> in your browser to see configured values at runtime.
<pre>
private static $config = array(
// edit values here // comment
// general configuration
'core' => array(true, 'enable or disable woogle at all'),
'replace' => array(true, 'replace built-in MediaWiki search'),
'advanced' => array(true, 'use Woogle "advanced" mode: redirection to an own wiki page for each search result'),
'advancedBox' => array(true, 'show the box for the "advanced" mode with the corresponding wiki content in it'),
'advancedWikiLink' => array(true, 'show a button to create a wiki page with the same name as the search string'),
'advancedWatch' => array(true, 'show a button to watch a search result for changes in the corresponding wiki page'),
'advancedDiscussion' => array(true, 'show a button including a link on the result\'s discussion page'),
'advancedNamespaceGrab' => array(true, 'if the (usually) Woogle:Namespace should be grabbed and redirected to the nonAdvanced url if advanced is turned off'),
'redLinkInfo' => array(false, 'show meta-info popups next to red links'),
'limitAccessToGroups' => array(false, 'access limited to mediawiki groups specified in $groups'),
'groups' => array(array('fzi'), 'groups access is limited to if $limitAccessToGroups'),
'defaultCount' => array(10, 'default number of results shown per page'),
'helpPage' => array('Woogle', 'wiki-page shown as help page'),
'resultWidth' => array(650, 'pixel-width of the result list'),
'searchOptions' => array('source=mediawiki', 'additional search options when using the built-in mediawiki search'),
'timeout' => array(0, 'timeout if the QueryService is down (in seconds)'),
'clickTracking' => array(true, 'if clicks are being tracked'),
'indexAddon' => array('Native', 'addon used for the Woogle index'),
'indexRepository' => array(17, 'repository id this wiki should use in the index')
);
</pre>

See the documentation for each value on the right side. Typically, there is '''no need to change most of these values'''. Values that required consideration are:
* <code>indexAddon</code> - put in 'Native' or 'Remote' depending on your choice of the backend!
* <code>indexRepository</code> - put in a numeric id. For WoogleNative it is arbitrary, for WoogleRemote you need to use the repoId configured in the backend (c.f. [[repo_config.xml]]

For WoogleRemote, you need to make additional settings (see below).

=== Specific settings for WoogleRemote ===
Edit <code>[Your MediaWiki directory]/extensions/Woogle/addons/Remote.php</code>.

<pre>
function woogleRemoteConfig(&$config) {
$config['remoteAuthKey'] = array("anonymous", 'authKey being passed to the remote Backend');
$config['remoteQueryServiceUrl'] = array('http://octopus13.fzi.de:9999/teamweaverIS-backend/services/phpQuery',
'remote query service url');
$config['remoteUpdateServiceUrl'] = array('http://octopus13.fzi.de:9999/teamweaverIS-backend/services/phpUpdate',
'remote update service url');
$config['remoteIndexServiceUrl'] = array('http://octopus13.fzi.de:9999/teamweaverIS-backend/services/phpIndex',
'remote update service url');
$config['remoteOptions'] = array(array('username' => 'waves', 'password' => 'trrwd'),
'options being passed to the HessianClient');
$config['remoteServiceName'] = array('Woogle', 'service name being passed to the wavesIS backend');
$config['remoteServiceVersion'] = array('0.99', 'service version being passed to the wavesIS backend');
$config['remotePushIndexAuthKey'] = array('dummyKey', 'key the push index is called with to authenticate');
return true;
}
</pre>

Values you need to configure:
* <code>remote...ServiceUrl</code> - set the respective backend URLs here
* <code>remotePushIndexAuthKey</code> - for indexing - as configured in the backend [[repo_config.xml]]
* <code>remoteAuthKey</code> - only required for querying, if the backend is set to securityEnabled = true;

== Deutsch (German) (nicht auf dem neuesten Stand) ==

=== Allgemeine Konfiguration ===

Die folgenden Einstellungen können in der Datei <code>[MediaWiki Installationverzeichnis]/extensions/Woogle/WoogleConfig.php</code> vorgenommen werden. Wenn Sie die Seite <code>[MediaWiki URL]/Special:WoogleConfig</code> in Ihrem Web-Broweser öffnen, können Sie die Konfigurationswerte zur Laufzeit sehen.
<pre>
private static $config = array(
// edit values here // comment
'advanced' => array(true, 'use Woogle "advanced" mode'),
'advancedBox' => array(true, 'show the box for the "advanced" mode with the corresponding wiki content in it'),
'advancedWikiLink' => array(true, 'show a button to create a wiki page with the same name as the search string'),
'advancedWatch' => array(true, 'show a button to watch a search result for changes in the corresponding wiki page'),
'advancedNamespaceGrab' => array(true, 'if the (usually) Woogle:Namespace should be grabbed and redirected to the nonAdvanced url if advanced is turned off'),
'limitAccessToGroups' => array(false, 'access limited to mediawiki groups specified in $groups'),
'groups' => array(array('fzi'), 'groups access is limited to if $limitAccessToGroups'),
'defaultCount' => array(10, 'default number of results shown per page'),
'helpPage' => array('Woogle', 'wiki-page shown as help page'),
'resultWidth' => array(650, 'pixel-width of the result list'),
'secure' => array(false, 'mediawiki being accessed with SSL'),
'searchOptions' => array('source=mediawiki', 'additional search options when using the built-in mediawiki search'),
'remoteQueryService' => array(false, 'query service remote or native - if set to false you can skip the rest of the configuration, but make sure to setup the native index with Special:WoogleNative'),
'authKey' => array("anonymous", 'authKey being passed to the remote Backend'),
'queryServiceUrl' => array('http://server:8080/teamweaverIS-backend/services/phpQuery',
'remote query service url, only relevant for the remote query service'),
'updateServiceUrl' => array('http://server:8080/teamweaverIS-backend/services/phpUpdate',
'remote update service url, only relevant for the remote query service'),
'indexServiceUrl' => array('http://server:8080/teamweaverIS-backend/services/phpIndex',
'remote update service url, only relevant for the remote query service'),
'options' => array(array('username' => 'waves', 'password' => 'trrwd'),
'options being passed to the HessianClient, only relevant for the remote query service'),
'clickTracking' => array(false, 'if clicks are being tracked, only relevant for the remote query service'),
'serviceName' => array('Woogle', 'service name being passed to the wavesIS backend, only relevant for the remote query service'),
'serviceVersion' => array('0.2 beta', 'service version being passed to the wavesIS backend, only relevant for the remote query service'),
);

* $groups: Array der erlaubten Mediawiki Benutzergruppen (wenn $limitAccessToGroups true ist)
* $limitAccessToGroups: limitiert den Zugriff auf die Woogle-Suche auf die Gruppen in $groups
* $clickTracking: ob click tracking aktiviert ist oder nicht
* $queryServiceUrl: die URL zum teamweaverIS Backend QueryService
* $updateServiceUrl: die URL zum teamweaverIS Backend UpdateService
* $options: Array mit Optionen fuer den Backend Service - z.B. wenn auf dem Tomcat die HTTP Authentifizierung aktiviert ist (Felder username und password)
* $serviceName: mit welchem Namen sich Woogle beim Backend authentifizieren soll
* $serviceVersion: mit welcher Version sich Woogle beim Backend authentifizieren soll
* $helpPage: auf welcher Wiki-Seite sich die Woogle-Hilfe befindet - gibt es keine einfach leer lassen
* $secure: ob Woogle hinter einer SSL-Verbindung ist
* $searchOptions: QueryString, der hinter Wikisuchen gehaengt wird (z.B. Parameter fuer die erweiterte Suche, sodass gleich nur in einer Quelle gesucht wird)

</pre>

=== Woogle über die MediaWiki Suchmaske aufrufen ===
* in der <code>[MediaWiki Installationverzeichnis]/index.php</code> folgende Zeile nach <code>require_once( './includes/WebStart.php' );</code> einfügen, falls die Woogle-Suche mit der Standard-Searchbox funktionieren soll:
** <code>WoogleConfig::initSearch();</code>

__NOTOC__

Wiquila

2009-06-17T09:33:57Z

ChristianRoehr: Created page with '''Wiquila – an extensible rich client for high-productivity, integration-friendly Wikis'' Wiquila is a rich client able to provide comfortable Wiki authoring either for “leg…'

''Wiquila – an extensible rich client for high-productivity, integration-friendly Wikis''

Wiquila is a rich client able to provide comfortable Wiki authoring either for “legacy” Wiki engines, or for the knowledge base we develop in the same project. Wiquila allows easy insertion of dynamically updated references to internal and external resources.

== Download and test drive ==
* Watch the screencast of an older release at http://www.teamweaver.org/downloads/media/screencasts/2007-12-10_wiquila_screencast/index.html (Demo starts at 6:40)
* Download from here: http://www.teamweaver.org/downloads/binaries/wiquila/
* unZip to local drive
* refer to readme.txt for further instructions for your environment
* by default, you will be able to access our public Wiki instance

== Challenges of using today's Wiki in an Enterprise context ==
A survey with our partners, some of whom have had extensive, enterprise-wide Wiki installations for years, as well as our own experience indicate that enterprises struggle with the following issues when using today’s Wikis:
Usability. The appearance of text completely changes between viewing and editing. Learning Wikisyntax is a slow process. No direct feedback is given, making errors more likely.

=== Productivity ===
Even those users who know Wikisyntax perfectly well lose time because common operations are more complicated than they need be (e.g. find&replace), and their attention is drawn away from the content itself to technicalities. This may be acceptable for a volunteer project like Wikipedia, where these difficulties may provide an element of identification of its members with “Wiki culture”, but it must be a real concern for enterprises whose goal is not the Wiki itself.

=== Rampant growth and other quality issues===
Large Wikis can quickly become poorly structured, if there are not volunteer “Wiki gardeners” who engage in cleaning up and direct communication with users. It is quite difficult to see the real structure of a Wiki from a distance, and to get an overview of all the available content, and the part that is still applicable, as a new user.
==== Integration ====
A Wiki today is, in a way, a silo of its own, whereas many large enterprises currently seek to reduce the number of applications and increase their integration. The only integration Wikis provide is being able to insert hyperlinks to other resources in the Enterprise which can be accessed via a browser, but even this process is fraught with difficulties, since URLs may contain session IDs. It can be often seen that information that is already available in other sources is manually replicated in the Wiki (in our specific case: phone numbers of employees).

=== Crossing company borders===
It is very hard to find satisfactory solutions when companies want to collaborate for some time. If only one partner hosts the solution, the other partners may be reluctant to contribute because they may not be able to access their contributions later. Single sign-on for several partners is hard to realize.

=== Offline access ===
Sales and management spend a lot of time on the road, and therefore need offline access and offline authoring capabilities, otherwise they will always stick with e-mail.

== Goals for Wiquila's design ==

Early in the project, we found it legitimate to look beyond pure browser-based interfaces, towards a more comfortable client. First, most other groupware (e-mail, IM) and document creation applications are installed on Desktops. Second, several Rich Internet Client technologies now exist which combine the Web’s ease of deployment with the Desktops richness of interaction.

The design goals for the Wiquila client were:
* Easy editing of formatted text
* Easy (assisted) insertion of links to Wiki pages and existing information objects
* High productivity for power users – no need to switch from the keyboard to the mouse for common actions
* Desktop integration (Drag&Drop, Copy&Paste)
* Built-in tools for quality analysis and improvement
* Extensibility to account for today’s heterogeneous environment
* Ability to be integrated as a component into Eclipse, and perhaps the Web browser
* Support for cross-company scenarios
* Possibility to access “legacy” wikis
* Scalability and performance
* Security
* Protocols can be accessed from similar clients which are based on different technology (.NET, AJAX)
* Robustness – the client works even if some of the integrated backend systems are not running

One of several driving use cases was the Meeting Minutes use case: A project team meets, at an early stage in the project, and meeting minutes are entered in the Wiki. These minutes contain some free-form text as well as “items”: Todos, Dates, Requirements, etc. We want to make it as easy as possible to create these structured items while entering the minutes, and also allow post-processing of minutes that where entered as a draft, perhaps offline. As the project matures, one may want to add additional structure and links to the minutes, to improve traceability of decisions.

Maven

2009-06-17T09:32:58Z

ChristianRoehr: Created page with 'The TeamWeaver build infrastructure is based on [http://maven.apache.org/ Apache Maven]. To create binaries for a certain TeamWeaver bundle call "mvn install" in its root direct…'

The TeamWeaver build infrastructure is based on [http://maven.apache.org/ Apache Maven].

To create binaries for a certain TeamWeaver bundle call "mvn install" in its root directory (the one containing the pom.xml file).

== Useful stuff ==

=== Arbitry/popular maven commands ===
* Create project
** mvn archetype:create ...
* Building
** mvn package (compile to create local build artifact)
** mvn install (mvn package plus install to local maven repository)
** mvn deploy (mvn install plus deploy to public maven repository)
* Release
** mvn release prepare
** mvn release perform
* Manage repository
** mvn install:install-file
** mvn deploy:deploy-file
* Eclipse
** mvn eclipse:eclipse (generate Eclipse .project files etc. for a maven project
** mvn eclipse:clean (remove Eclipse .project files etc
* Other
** mvn clean (remove build artifacts)
** mvn javadoc:javadoc (generate javadoc)
** mvn jetty:run

=== Q&A ===
* Maven gets me a Java OutOfMemory Exception
** Increase heap space by setting the environment variable "MAVEN_OPTS" to e.g. "-Xmx1024m -Xms512m"

=== Links ===
* [http://www.mvnrepository.com/ Maven artifact search engine]

Integrated Search/Supported data sources

2009-06-17T09:32:38Z

ChristianRoehr: Created page with 'TeamWeaverIS supports to crawl/index various types of data sources listed on this page. For configuration of the data sources to index with TeamWeaver, see repo_config.xml. …'

TeamWeaverIS supports to crawl/index various types of data sources listed on this page. For configuration of the data sources to index with TeamWeaver, see [[repo_config.xml]].

== Data sources ==

=== General sources ===
* File systems and network shares
* Web ressources (web sites, but also other file formats (see below))
* SVN repositories
* CVS repositories
* Microsoft SourceSafe repositories

=== Specific sources ===
* Various Ticketing systems (Buzzilla, Atlassian JIRA, OTRS)
* Various Wiki systems (Mediawiki, JSPWiki, Atlassian Confluence)
* XPlanner
* E-Mail (IMAP, Microsoft Outlook)
* Cobra Adressmanager
* CAS genesisWorld
* JDBC-accisible databases (allows to easily write own crawlers for data stored in databases)
* tbc.

== File formats ==
* HTML
* Office (DOC, XLS, PPT, Visio)
* PDF
* Text-Files including Source Code
* tbc.

Integrated Search/Download

2009-06-17T09:32:04Z

ChristianRoehr: Created page with '== Binary downloads == * TeamWeaver Integrated Search ** version 0.9.8 http://www.teamweaver.org/downloads/binaries/is/wavesIS_0.9.8.zip (as of 2008-10-14) ** version 0.9.9 h…'

== Binary downloads ==
* TeamWeaver [[Integrated Search]]
** version 0.9.8 http://www.teamweaver.org/downloads/binaries/is/wavesIS_0.9.8.zip (as of 2008-10-14)
** version 0.9.9 http://www.teamweaver.org/downloads/binaries/is/teamweaverIS_0.9.9.zip (as of 2009-04-08)
* [[Woogle]]
** [[Woogle4MediaWiki]] (tbd.)

== Source code download ==
tbd.

Integrated Search

2009-06-17T09:31:20Z

ChristianRoehr: Created page with 'TeamWeaver Integrated Search provides an integrated crawling and search mechanism across multiple software-engineering related data such as repositories (SVN, CVS, SourceSafe, Fi…'

TeamWeaver Integrated Search provides an integrated crawling and search mechanism across multiple software-engineering related data such as repositories (SVN, CVS, SourceSafe, Filesystems) filetypes (Code, Office-Documents, PDF) and various systems (e.g. JIRA, Bugzilla, OTRS, Confluence, MediaWiki, XPlanner).

TeamWeaver Integrated Search can be accessed via a web-frontend, embedded into a MediaWiki instance, or from within Eclipse.

== Dowloadable evaluation Demo ==
An evaluation demo of TeamWeaver IS is available on the [[Integrated Search/Download|download page]].

Documentation
* [[Integrated_Search/Installation|Installation guide]]
* [[Integrated_Search/Configuration|Configuration guide]]

== Online Demo ==
An online demo can be accessed at http://octopus18.fzi.de:8080/wavesIS/

== Build ==
* In order to create your own build of the TeamWeaver sources you need to install the [[Maven]] build system on your machine and to checkout the following two projects
** http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/org.teamweaver.dist.is.backend.war/
** http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/org.teamweaver.is.frontend.eclipse/ (for the Eclipse client)
* Run "mvn install" in both directories after checkout, to generate the build artifacts in the \target folder

Airmail

2009-06-17T09:30:47Z

ChristianRoehr: Created page with ''''NOTICE: This page was created by a program as part of the Graffiti Network research project at Brown University. We have removed the data, but are unable to remove this page. …'

'''NOTICE: This page was created by a program as part of the Graffiti Network research project at Brown University. We have removed the data, but are unable to remove this page. We apologize for any inconveniences that our actions may have caused. For more information, please visit [http://graffiti.cs.brown.edu/522e1b727e4132a8100774905055f999/info/ http://graffiti.cs.brown.edu/info/].'''

Woogle4MediaWiki/Compability

2009-06-17T09:30:13Z

ChristianRoehr: Created page with '== Compability with MediaWiki == Due to required [http://www.mediawiki.org/wiki/Manual:Hooks Hooks], Woogle4MediaWiki requires MediaWiki in a version >= 1.11.0. It should be theo…'

== Compability with MediaWiki ==
Due to required [http://www.mediawiki.org/wiki/Manual:Hooks Hooks], Woogle4MediaWiki requires MediaWiki in a version >= 1.11.0. It should be theoretically possible to make (parts of) Woogle compatible with earlier versions of MediaWiki by modifying the sources.

Woogle is currently tested up to MediaWiki version 1.14.0. (which is the recent version as of 2009-04-08). There is no fundamental reason, why it should not work with future versions of MediaWiki, although we can not gurantee that.

Other explicit version were are/were developing/testing with (incomplete list):
* MediaWiki 1.11.0
* MediaWiki 1.13.3

== Compability with Web servers/PHP/mySQL ==
Woogle should work fine in any server environment in which the embedding MediaWiki works. In particular, we are using the following environments (incomplete list):
* CentOS Linux machine (Apache / PHP: 5.1.6 (apache2handler) / MySQL: 5.0.45)
* Windows 2000 Server (Apache / PHP 5.2.6 (apache2handler) / MySQL 5.0.45-community-nt)
* Windows Vista (ApacheFriends XAMPP version 1.7.0 / PHP 5.2.8 (apache2handler) / mySQL 5.1.30-community)

Repo config.xml

2009-06-17T09:29:49Z

ChristianRoehr: Created page with 'The file <code>repo_config.xml</code> in the <code>\teamweaverIS-backend\WEB-INF\conf</code> of your TeamWeaverIS backend allows you to define …'

The file <code>repo_config.xml</code> in the <code>\teamweaverIS-backend\WEB-INF\conf</code> of your [[Integrated Search/Installation|TeamWeaverIS backend]] allows you to define [[Integrated Search/Supported data sources|data sources]] to be crawled.

Users can easily develop an plug in crawlers for other data sources. See our [[Integrated Search/How to write a custom crawler|guide how to write a custom crawler]].

Repositories are crawled by assigning them to a [[crawl_config.xml|crawl]].

== Example <code>repo_config.xml</code> ==
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<repo_config>
<repositoryInfo>
<repoId>1</repoId>
<repoName>PushIndexingTestRepo</repoName>
<srcType>web</srcType>
<srcVersion>1.0</srcVersion>
<connectURL>http://www.teamweaver.org/</connectURL>
<connectType>http</connectType>
<user></user>
<pass></pass>
<group>all</group>
<linkPath></linkPath>
<pushIndexAuthKey>test42</pushIndexAuthKey>
<pushIndexEnabled>true</pushIndexEnabled>
<cacheFulltext>true</cacheFulltext>
</repositoryInfo>
<repositoryInfo>
<repoId>2</repoId>
<repoName>files</repoName>
<srcType>filesystem</srcType>
<srcVersion>1.0</srcVersion>
<connectURL>//linde/c$/docs_small</connectURL>
<connectType>filesystem</connectType>
<linkPath>http://webdav.internal.de/linde/c/docs_small/</linkPath>
<user></user>
<pass></pass>
<group>all</group>
</repositoryInfo>
</repo_config>
</pre>

== Documentation of parameters ==
* <code>repo_config.xml</code> contains <code><repositoryInfo></code> entries for each single repository to be crawled (see example file above)
* For specific information about the semantics of parameters in the context of different source types consult the "List of Source Types" below
* The parameters inside the <code><repositoryInfo></code> element are as follows:
** <code><repoId>1</repoId></code> - denotes a numerical id for the repository. This needs to be unique within the repositoryInfo elements of the <code>repo_config.xml</code>
** <code><repoName>My Test repository</repoName></code> - a human readable label for the repository
** <code><srcType>web</srcType></code> - denotes the type of repository - see below for a list of allowed keys
** <code><srcVersion>1.0</srcVersion></code> - denotes a version of the repository type - irrelevant for most types ('''OPTIONAL''')
** <code><connectURL>http://www.teamweaver.org/</connectURL></code> - a descriptor of the physical location. The exact form depends on the kind of srcType - e.g. for a "web" ressource, this is a URL, while for a file system, it is a path
** <code><connectType>http</connectType></code> - denotes a conncection mode for srcTypes that allow for a choice - irrelevant for most types ('''OPTIONAL''')
** <code><user>myUser</user></code> - user name, if the srcType requires authentification ('''OPTIONAL''')
** <code><pass>myPass</pass></code> - password ('''OPTIONAL''')
** <code><group>all</group></code> - user group for which the crawled data for this entry should be accessible ('''OPTIONAL''')
** <code><linkPath></linkPath></code> - allows to specify a separate "link path" for repositories, which do not provide "clickable" URLs for the browser. E.g. a network file share might by indexed as <code>\\computer\path\</code> which is typically not clickable in a web result list. Therefore you could provide an alternative link path to the repository (e.g. a WebDAV wrapper) - <code>http://internal.mycompany.de/computer/path/</code> which is then used to refere to results. ('''OPTIONAL''')
** <code><cacheFulltext>false</cacheFulltext></code> - denotes if the backend should cache indexed files in order to make them accessible via the result interface. This is an alternative, if it not possible to expose those systems via the <code><linkPath></code> option.
** <code><pushIndexEnabled>false</pushIndexEnabled></code> - if set to true, this repository can not be actively crawled any more using [[crawl_config.xml]], but will instead push changes to the backend ('''OPTIONAL''')
** <code><pushIndexAuthKey>a_password</pushIndexAuthKey></code> - an arbitrary string which servers for authentification of the push indexing client ('''OPTIONAL''')

== List of Source Types ==
This is the list of allowed <code><srcType></code> attributes for a <code><repositoryInfo></code> entry. The complete authoritative list can be obtained from the [http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/org.teamweaver.is.backend.crawl/src/main/java/org/teamweaver/is/backend/crawl/aperture/crawler/defaultCrawlers.xml defaultCrawlers.xml] in the SVN.

=== Web ressources ("web") ===
* <code><repositoryInfo></code> options
** <code><srcType>web</srcType></code>
** <code><connectURL>http://www.fzi.de/ipe/</connectURL></code>
* Behaviour: the web crawler in its current state of implementation starts from the initial page defined by the <code>connectURL</code> and follows all links including resp. starting with <code>connectURL</code> (e.g. <code>http://www.fzi.de/ipe/some_subdirectory/page.html</code> but not <code>http://www.fzi.de/se/page.html</code>) up to a depth of 9 hops. There is currently no way to configure a different behaviour (although this could be implemented fairly easy).

=== File systems/network shares ===
* <code><repositoryInfo></code> options
** <code><srcType>filesystem</srcType></code>
** <code><connectType>filesystem</connectType></code> (Example)
** <code><linkPath>http://webdav.internal.de/linde/c/docs_small/</linkPath></code> (Example)

=== SVN repositories ===
* <code><repositoryInfo></code> options
** <code><srcType>svn</srcType></code>
** <code><connectURL>http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/</connectURL></code> (Example)
*** <code><connectURL>svn+ssh://anonymous@ontoware.org/svnroot/semweb4j/trunk</connectURL></code> (Alternative Example)
** <code><connectType>http</connectType></code>

=== CVS repositories ===
* <code><repositoryInfo></code> options
** <code><srcType>svn</srcType></code>
** <code><connectURL>:pserver:anonymous@aperture.cvs.sourceforge.net:/cvsroot/aperture:aperture</connectURL></code> (Example)
** <code><connectType>pserver</connectType></code>

=== Atlassian Confluence Wiki ===
* <code><repositoryInfo></code> options
** <code><srcType>confluence</srcType></code>
** <code><connectURL>http://localhost:8080/confluence/</connectURL></code> (Example)
** <code><connectType>rpc</connectType></code>

=== Atlassian Jira Issue Tracker ===
* <code><repositoryInfo></code> options
** <code><srcType>jira</srcType></code>
** <code><connectURL>localhost:8080/</connectURL></code> (Example)
** <code><connectType>rpc</connectType></code>

=== JSPWiki ===
* <code><repositoryInfo></code> options
** <code><srcType>jspwiki</srcType></code>
** <code><srcVersion>2.0</srcVersion></code>
** <code><connectURL>http://www.jspwiki.org</connectURL></code>
** <code><connectType>rpc</connectType></code>

=== Bugzilla Issue Tracker ===
* <code><repositoryInfo></code> options
** <code><srcType>bugzilla</srcType></code>
** <code><connectURL>http://landfill.bugzilla.org/bugzilla-2.18-branch/</connectURL></code> (Example)
** <code><connectType>rpc</connectType></code>

=== To be continued.... ===
* To be continued....

Integrated Search/Installation

2009-06-17T09:29:09Z

ChristianRoehr: Created page with 'This page describes how to setup TeamWeaver Integrated search in various flavours. == Server Backend == The TeamWeaverIS backend is the core component of Integrated Search. It m…'

This page describes how to setup TeamWeaver Integrated search in various flavours.

== Server Backend ==
The TeamWeaverIS backend is the core component of Integrated Search. It maintains an index, which can be built by crawling various different [[Integrated Search/Supported data sources|supported data sources]]. The backend offers services, which can be used by one of the client frontends (JSF-Frontend, Eclipse-based frontend or [[Woogle|Wiki-based frontend]]) to query and display search results.

The following steps are required for installation:
* Prepare a Java Web Application Server (usually, the latest [http://tomcat.apache.org/ Apache Tomcat] will do; see [[Integrated Search/Compatibility|supported Web Application Servers]])
** Tomcat comes as a ZIP distribution and installation is typically not more than unzipping. In the following, we will assume you chose Tomcat as your Web Application Server - however everything works very similar with other systems such as [http://jetty.mortbay.com/jetty/ Jetty].
* [[Integrated Search/Download|Download]] the latest version of the backend
* Copy the file <code>teamweaverIS-backend.war</code> to the <code>webapps</code> folder of your Tomcat
* Start the Tomcat once. It will then "deploy" the WAR-archive and automatically create a separate folder <code>teamweaverIS-backend</code> in the <code>webapps</code> folder.
** Note: Tomcat can run as an application (using <code>webapps</code>startup.bat<code>webapps</code> resp. <code>webapps</code>startup.sh<code>webapps</code> scripts) or as a service
* Stop the Tomcat again.
* You may now proceed with the [[Integrated Search/Configuration|configuration]].
* After configuration, you can start Tomcat again. After configuration and initial crawling, you can start Tomcat again. The TeamWeaverIS server backend is configured to provide indexing and search functionility as a web service. You can use any TeamWeaverIS frontend to connect to your service. When the Tomcat runs on your local machine, the service URL should be: '''<code>http://localhost:8080/teamweaverIS-backend/services/query</code>''', unless you configured Tomcat to run on another port.

== Frontends ==
Chose any (or multiple) of these frontends to access search results from your TeamWeaverIS backend.

=== JSF Frontend ===
The JSF-Frontend is the default frontend for the server backend. It is also deployed in a Java Web Application Server (usually, but not necessarily the same as the backend) and offers a "Google-style" browser-based search interface to access data from a backend.

The following steps are required for installation:
* Prepare a Java Web Application Server (see installation steps for the backend; we recommend to use the same server as for the backend)
* [[Integrated Search/Download|Download]] the latest version of the JSF-frontend
* Copy the file <code>teamweaverIS.war</code> to the <code>webapps</code> folder of your Tomcat
* Start the Tomcat once. It will then "deploy" the WAR-archive and automatically create a separate folder <code>teamweaverIS</code> in the <code>webapps</code> folder.
* Stop the Tomcat again.
* If you run the frontend in a different Tomcat than the backend, '''or''' if your Tomcat uses another port than the default 8080, you need to edit the server URLs in the configuration file <code>\webapps\teamweaverIS\WEB-INF\queryWSClient.xml</code>
* You can then start the Tomcat again to use the JSF frontend. You can now open the JSF-frontend URL in your browser. If you run the Tomcat on your localhost, this will typically be http://localhost:8080/teamweaverIS/. The result should look like this site: http://octopus18.fzi.de:8080/wavesIS/.

=== (Media) Wiki Frontend ===
You may search and display results from a TeamWeaverIS server backend within a MediaWiki instance. In this scenario, TeamWeaverIS completely replaces the built-in Wiki-search - i.e. changes in the Wiki directly reflect in the TeamWeaverIS backend index.

An implementation for MediaWiki is availalbe and fairly stable, while an implementation for the Atlassian Confluence wiki engine is currently under development. See [[Woogle]] for more details.

=== Eclipse Plugin ===
TeamWeaverIS can also be integrated into the Eclipse IDE. Both functionalities - crawling and searching - are supported within Eclipse. We currently do not offer separate/modularized distributions. However, you can neglect crawling features in Eclipse when you just want to use it as a serch UI for a server backend.

The current (unstable) update site URL is http://www.teamweaver.org/downloads/eclipse-update-site/2008-10-27-twIS-098/. Note that the Eclipse plugin might not yet be ready for production use. The plugin is tested with Eclipse 3.4 (Ganymede) and 3.3 (Europa) and will most probably run on Eclipse 3.2 as well. Note that the update site size is around 30MB - installation might thus take some time.

We also have an experimental Eclipse RCP (desktop) application.

Integrated Search/Configuration

2009-06-17T09:28:42Z

ChristianRoehr: Created page with '== Server Backend == The backend needs some basic configuration to configure data sources that should be crawled. === Configure data sources === * For configuration, make sure t…'

== Server Backend ==
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 <code>\teamweaverIS-backend\WEB-INF\conf</code>
* In here, you find (among other) two configuration files, which you need to edit:
** <code>repo_config.xml</code> contains access data for the repositories you want to crawl (see [[repo_config.xml]] for details)
** <code>crawl_config.xml</code> 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 <code>teamweaverIS-backend</code> folder and execute <code>cc.bat</code> resp. <code>cc.sh</code>. This will generate some scripts required for crawling.
* Execute the crawl shell script (<code>crawl.bat</code> resp. <code>crawl.sh</code> with the Id of the crawl you want to execute (as defined in [[crawl_config.xml]]) - e.g. "<code>crawl 0</code>"
** 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 Enterprise|Polarion]] and for [[Woogle|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 <code>pushIndexAuthKey</code> (see [[repo_config.xml]]).

For configuring the data source system, you need the following information:
* the backend URL (e.g. <code>http://localhost:8080/teamweaverIS-backend/services/</code>)
* the repositoryId and
* the <code>pushIndexAuthKey</code> as defined in the backend

The actual way of configuration should be described in the documentation. See e.g. [[Woogle4MediaWiki/Configuration]].

Eureka

2009-06-17T09:28:17Z

ChristianRoehr: Created page with 'Eureka is an Eclipse plugin for scientifc evaluation purposes, which monitors developers activities and compares them with a written log. The evaluation is currently closed and …'

Eureka is an Eclipse plugin for scientifc evaluation purposes, which monitors developers activities and compares them with a written log.

The evaluation is currently closed and we are analyzing the data. However, we are seeking volunteers to participate in upcoming evaluations.

Evaluation material and software can be accessed in the meanwhile for testing purposes.

== Material of the first evaluation round ==
* [http://www.teamweaver.org/downloads/binaries/eureka/v1//eureka_intro.pdf Eureka introduction slides]
* [http://www.teamweaver.org/downloads/binaries/eureka/v1/eureka_screenshots.pdf Eureka screenshots]
* [http://www.teamweaver.org/downloads/binaries/eureka/v1/eureka_intro.avi Eureka instruction Video]
* [http://www.teamweaver.org/downloads/binaries/eureka/v1/1.0/ Eureka Eclipse update site]
** * [http://www.teamweaver.org/downloads/binaries/eureka/v1/1.0.1/ Eureka Eclipse update site (without browser sensor)] (browser sensor was buggy in some setups)

2008-11-26 Eclipse DemoCamp Munich

2009-06-17T09:27:38Z

ChristianRoehr: Created page with '== "When Enterprise Search, Wikis & Co. go Eclipse" == Demo given at the third [http://wiki.eclipse.org/Eclipse_DemoCamps_November_2008/Munich Eclipse DemoCamp Munich]. Since s…'

== "When Enterprise Search, Wikis & Co. go Eclipse" ==
Demo given at the third [http://wiki.eclipse.org/Eclipse_DemoCamps_November_2008/Munich Eclipse DemoCamp Munich].

Since software development projects typically contain lots of digital artifacts and various supporting systems such as Repositories, Issue Trackers and Wikis, searching and accessing this existing information is an important building block. Therefore, TeamWeaver [[Integrated Search]] allows to extract information from various software project data sources (e.g. SVN, CVS, Filesystem, Bugzilla, JIRA and various Wikis).
* Screencast: [http://www.teamweaver.org/downloads/media/screencasts/2008-10-30_integrated_search.avi TeamWeaver Integrated Search backend & browser-based client]

However, certain information - especially episodic "how-to" knowledge - might not be captured within an organization, or hidden on the local machines of certain developers. Therefore, TeamWeaver Integrated search can also be deployed as a kind of Eclipse-based Desktop Search Engine, to access local data of a developer.
* Screencast: [http://www.teamweaver.org/downloads/media/screencasts/2008-10-30_search_from_eclipse.avi Accessing a TeamWeaverIS server from within Eclipse]

On top of this infrastructure, the [[Inverse Search]] method tries to provide individual developers with clues which information is sought within an organization, and provides concrete recommendations on local documents which are worth sharing
* Screencast: [http://www.teamweaver.org/downloads/media/screencasts/2008-10-30_inverse_search.avi Inverse Search]

Finally, it can be useful for developers, to know which colleagues are experienced with a certain library, class or method. To this end, TeamWeaver monitors individual user's coding experience and allows them to share this with their colleagues. Embedded in the Eclipse coding help, developers can quickly recognize, which collegue is knowledgeable about a certain piece of code.
* Screencast: [http://www.teamweaver.org/downloads/media/screencasts/2008-10-22_reuse_experience_screencast.mov Eclipse Reuse Experience]

Here is also a copy of our flyer: [http://www.teamweaver.org/downloads/media/docs/2008-10-31_DemoCamp_Flyer.pdf TeamWeaver general information sheet]

[[Category:Event]]

Woogle4MediaWiki/Installation

2009-06-17T09:26:54Z

ChristianRoehr: Created page with '== English == Before starting, it is important to understand that Woogle4MediaWiki can be run in '''two different modes''': * WoogleNative - which is pure PHP-based - you can onl…'

== English ==
Before starting, it is important to understand that Woogle4MediaWiki can be run in '''two different modes''':
* WoogleNative - which is pure PHP-based - you can only search and index your Wiki as such, but no data outside the Wiki
* WoogleRemote - which connects to a [[Integrated Search]] backend - you can search any kind of data indexed by the backend (including e.g. file systems, SVN ressources etc.)

=== Prerequisites ===
* Woogle4MediaWiki requires [http://www.mediawiki.org/wiki/MediaWiki MediaWiki] in a version >= 1.11.0 (see also [[Woogle4MediaWiki/Compability|compatibility notes]])
* For WoogleNative (see above) you need
** A database user with CREATE TABLE privileges (or the database root account)
* For WoogleRemote you need
** An installed [[Integrated Search]] backend, and some configuration data (backend URL, repoId, pushIndexAuthKey; c.f. [[http://www.teamweaver.org/wiki/index.php/Integrated_Search/Configuration#Configuring_.22push.22_indexing|for push indexing]])

=== Installation steps ===
* Extract the content of the Woogle distribution ZIP-file to <code>[Your MediaWiki directory]/extensions/Woogle</code>
* Grant write permissions for the executing user on <code>[Your MediaWiki directory]/extensions/Woogle/addons/Native/index</code>, if you're using the Native addon
* At the end of the file <code>[Your MediaWiki directory]/LocalSettings.php</code> add the following line: <code>include_once('extensions/Woogle/Woogle.php' ); </code>
* [[Woogle4MediaWiki/Configuration|Configure]] everything
* Open <code>[MediaWiki URL]/Special:WoogleConfig</code> in your browser and click "index" to create an initial index
* Enter <code>[MediaWiki URL]/index.php/Special:Woogle</code> to your browser to check if everything works

== Deutsch (German) (nicht auf dem neuesten Stand) ==
* Den Inhalt der Woogle ZIP-Datei nach <code>[MediaWiki Installationverzeichnis]/extensions/Woogle</code> entpacken
* Dem ausführenden Benutzer Schreibrechte in <code>[MediaWiki Installationverzeichnis]/extensions/Woogle/addons/Native/index</code> gewähren, sofern das Native Addon benutzt wird
* Am Ende der Datei <code>[MediaWiki Installationverzeichnis]/LocalSettings.php</code> folgende Zeile einfügen:
** <code>include_once('extensions/Woogle/Woogle.php' ); </code>
* [[Woogle4MediaWiki/Configuration|Konfigurieren]] Sie Woogle
* Öffnen Sie die URL <code>[MediaWiki URL]/Special:WoogleConfig</code> und clicken Sie "index" um den Inhalt des Wikis initial zu indexieren
* Öffnen Sie die URL <code>[MediaWiki URL]/index.php/Special:Woogle</code> in Ihrem Web-Browser um zu sehen, ob die Installation funktioniert hat

Woogle

2009-06-17T09:26:13Z

ChristianRoehr: Created page with 'Woogle is a concept for accessing TeamWeaver Integrated Search through a Wiki interface. There is currently a reference implementation as a [http://www.mediawiki.org MediaWi…'

Woogle is a concept for accessing TeamWeaver [[Integrated Search]] through a Wiki interface.

There is currently a reference implementation as a [http://www.mediawiki.org MediaWiki] extension, which is not publically released yet. Feel free to contact us, if you like further information.

== Woogle4MediaWiki ==
* General information
** [http://www.slideshare.net/hhappel/woogle-on-why-and-how-to-marry-wikis-with-enterprise-search Presentation slides]
** Live-Demo: see [[Special:Woogle]]
* Adminstrative information
** [[Woogle4MediaWiki/Installation|Installation]]
** [[Woogle4MediaWiki/Configuration|Configuration]]

Woogle4MediaWiki is currently in a '''beta phase'''. The system is stable enough to run in actual MediaWiki installations (MediaWiki v1.11 required). We are currently '''seeking interested organizations using MediaWiki''' who would like to test Woogle in their environment.

== Woogle4Confluence ==
* under construction

News and Events

2009-06-17T09:25:42Z

ChristianRoehr: Created page with '* 2009-06-03 At least 3 TeamWeaver developers will take part at the [Eclipse Galileo DemoCamp in Munich http://wiki.eclipse.org/Eclipse_DemoCamps_Galileo_2009/Munich] * 2009-05-1…'

* 2009-06-03 At least 3 TeamWeaver developers will take part at the [Eclipse Galileo DemoCamp in Munich http://wiki.eclipse.org/Eclipse_DemoCamps_Galileo_2009/Munich]
* 2009-05-18 A scientific study, which lays the work description feature (under development) was presented at the IEEE Inter. Conference on Mining Software repositories in Vancouver [http://msr.uwaterloo.ca/msr2009/msr09-schedule.pdf]
* 2009-03-26 The [[Woogle]] interface for TeamWeaver was presented at the 5th Conference on Professional Knowledge Management in Switzerland
* 2008-10-27 TeamWeaver new features will be demonstrated at the third [http://wiki.eclipse.org/Eclipse_DemoCamps_November_2008/Munich Munich Eclipse Democamp] on November 26th ([[2008-11-26 Eclipse DemoCamp Munich|Screencasts]])
* 2008-10-27 The current state of TeamWeaver will be demonstrated at the third [http://wiki.eclipse.org/Eclipse_DemoCamps_November_2008/Karlsruhe Eclipse DemoCamp Karlsruhe] on October 30th ([[2008-10-30 Eclipse DemoCamp Karlsruhe|Screencasts]])
* 2008-10-14 Eclipse regulars' table in Munich [http://www.microdoc.com/node/287] . TeamWeaver is represented by Walid
* 2008-06-30 TeamWeaver will be presented at [http://wiki.eclipse.org/Eclipse_DemoCamps_2008_-_Ganymede_Edition/Munich Eclipse DemoCamp Munich]
* 2008-06-26 TeamWeaver will be presented at [http://wiki.eclipse.org/Eclipse_DemoCamps_2008_-_Ganymede_Edition/Karlsruhe Eclipse DemoCamp Karlsruhe]
* 2008-06-26 Launch auf teamweaver.org. Expect more content in the upcoming weeks!

Mailinglists

2009-06-17T09:25:02Z

ChristianRoehr: Created page with '== Annoucement == TeamWeaver Announcement Mailinglist (~1 Mail per Month; only announcements about new releases for end users). http://groups.google.com/group/teamweaver-ann If…'

== Annoucement ==

TeamWeaver Announcement Mailinglist (~1 Mail per Month; only announcements about new releases for end users).
http://groups.google.com/group/teamweaver-ann
If you wand to register please send a short email to maalejwYinXtumXde (let Y in @ and X in . )

== Developement ==

TeamWeaver Developer Mailinglist (high traffic, several emails per day).
http://groups.google.com/group/teamweaver-dev

If you wand to register please send a short email to maalejwYinXtumXde (let Y in @ and X in . )

Integrated Search/How to write a custom crawler

2009-06-17T09:24:39Z

ChristianRoehr: Created page with 'This short guide describes how to write crawlers to make additional data sources available for searching with TeamWeaver Integrated Search. A list of existing crawlers can b…'

This short guide describes how to write crawlers to make additional data sources available for searching with TeamWeaver [[Integrated Search]].

A list of existing crawlers can be found at: [[Integrated_Search/Supported_data_sources|supported data sources]] resp. [[repo_config.xml]].

There are two general strategies for crawling data sources with TeamWeaverIS:
* "Pull"-Crawlers are included in TeamWeaverIS and allow to crawl/extract data by accessing external sources/system. Pull-crawlers are fairly easy to realize, but have the disadvantage, that the index might not be accurate, since TeamWeaverIS does only learn about data changes, when a crawl is executed.
* "Push"-Crawlers are implemented on the side of the client system which includes the data. They proactively update the index and thus have a direct connection to the TeamWeaverIS backend. Accordingly, push-crawlers are more difficult to implement, but can reflect changes in the data more rapidly in the index.

== Writing a "Pull"-Crawler ==
At the basic level, creating a pull-crawler requires to implement two Java classes and changing two XML-files - a ''Crawler'' and a ''Processor'' each. Crawlers are classes which access a data source and extract/create single data items. Processors act upon these items to prepare them for feeding into the index.

=== Crawler ===
* You need to create a subclass of [http://aperture.sourceforge.net/doc/javadoc/org/semanticdesktop/aperture/crawler/base/CrawlerBase.html CrawlerBase] which basically means to implement a method <code>crawlObject</code>. See our [http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/org.teamweaver.is.backend.crawl/src/main/java/org/teamweaver/is/backend/crawl/aperture/crawler/JiraCrawler.java JIRACrawler] for an example.
* Afterwards, register your new crawler in [http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/org.teamweaver.is.backend.crawl/src/main/java/org/teamweaver/is/backend/crawl/aperture/crawler/defaultCrawlers.xml defaultCrawlers.xml]. You need to define a unique <code><repoType></code> key, which corresponds to the <code><srcType></code> in [[repo_config.xml]].

=== Processor ===
* You need to create a subclass of [http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/org.teamweaver.is.backend.crawl/src/main/java/org/teamweaver/is/backend/crawl/processor/impl/ProcessorBase.java ProcessorBase]. See our [http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/org.teamweaver.is.backend.crawl/src/main/java/org/teamweaver/is/backend/crawl/processor/impl/JiraProcessor.java JIRAProcessor] as an example.
* Afterwards, register your new processor in [http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/org.teamweaver.is.backend.crawl/src/main/java/org/teamweaver/is/backend/crawl/processor/impl/defaults.xml defaults.xml] by wiring it with the corresponding crawler.

=== Advanced topics ===
* tbd. (generic JDBC crawler)

== Writing a "Push"-Crawler ==
* tbd.
* Push-Crawlers have to call the TeamWeaver backend's [http://svn.polarion.org/repos/community/Teamweaver/Teamweaver/trunk/org.teamweaver.is.api/src/main/java/org/teamweaver/is/api/IndexService.java IndexService]
* You might want to look at our [[Woogle]] code for an example implementation of a push-crawler

Integrated Search/Compatibility

2009-06-17T09:24:02Z

ChristianRoehr: Created page with '== Compatibility with Web Application Servers == If you want to deploy Integrated Search as a server application, you need a Java Servlet Container/Web Application Server. So…'

== Compatibility with Web Application Servers ==
If you want to deploy [[Integrated Search]] as a server application, you need a Java Servlet Container/Web Application Server. So far, we made experiences using [http://tomcat.apache.org/ Apache Tomcat] and [http://www.mortbay.org/jetty/ jetty].

This section lists more specific issues about compatibility/non-compatibility:
* Try to prefer the most recent Tomcat Version (6.X). However, Tomcat 5.5 might also work
* tbd.

== Compatibility with Eclipse ==
This section lists experience about deploying TeamWeaver as an Eclipse plugin within an existing Eclipse application. Note that there is also a RCP-bundling of TeamWeaver, which acts as a standalone version including Eclipse runtime.

This section lists more specific issues about compatibility/non-compatibility:
* TeamWeaver was never tested in Eclipse versions lower than 3.2
* TeamWeaver should generally work in Eclipse versions 3.3, 3.4 and probably in later ones
* tbd.

Crawl config.xml

2009-06-17T09:23:14Z

ChristianRoehr: Created page with 'The file <code>repo_config.xml</code> in the <code>\teamweaverIS-backend\WEB-INF\conf</code> of your TeamWeaverIS backend allows you to group r…'

The file <code>repo_config.xml</code> in the <code>\teamweaverIS-backend\WEB-INF\conf</code> of your [[Integrated Search/Installation|TeamWeaverIS backend]] allows you to group repositories to be crawled (c.f. [[repo_config.xml]]) into "crawls" which can be triggered by the [[Integrated Search/Configuration|TeamWeaverIS backend]].

You need at least one crawl to be defined in order to be able to crawl data sources. Defining multiple crawls makes sense, if you would like to group repositories to treat them differently - e.g. one group of repositories to be crawled only once a week while another one is crawled every night.

== Example <code>crawl_config.xml</code> ==
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<crawl_config>
<crawlInfo>
<crawlId>0</crawlId>
<crawlName>nightly crawl</crawlName>
<updateFrequency>3600000</updateFrequency>
<repositoryIds>
<repositoryId>1</repositoryId>
<repositoryId>2</repositoryId>
<repositoryId>3</repositoryId>
</repositoryIds>
</crawlInfo>
</crawl_config>
</pre>

== Documentation of parameters ==
* <code>crawl_config.xml</code> contains <code><crawlInfo></code> entries for each single crawl that should be possible to start from the command line ("<code>crawl.bat 0</code>")
* The parameters inside the <code><crawlInfo></code> element are as follows:
** <code><crawlId>0</crawlId></code> - unique numeric id of the crawl which is used from the command line to reference the crawl
** <code><crawlName>nightly crawl</crawlName></code> - human readable description for logging/documentation purposes
** <code><updateFrequency>3600000</updateFrequency></code> - parameter is currently not used ('''OPTIONAL''')
** <code><repositoryIds><repositoryId>1</repositoryId><repositoryId>2</repositoryId><repositoryId>3</repositoryId></repositoryIds></code> - insert one <code><repositoryId></code> element for each repository to be included in that crawl (use the Id define int [[repo_config.xml]] for referencing)

2008-10-30 Eclipse DemoCamp Karlsruhe

2009-06-17T09:22:46Z

ChristianRoehr: Created page with '== "TeamWeaver4Eclipse - Knowledge sharing in distributed software teams" == Demo given at the third [http://wiki.eclipse.org/Eclipse_DemoCamps_November_2008/Karlsruhe Eclipse D…'

== "TeamWeaver4Eclipse - Knowledge sharing in distributed software teams" ==
Demo given at the third [http://wiki.eclipse.org/Eclipse_DemoCamps_November_2008/Karlsruhe Eclipse DemoCamp Karlsruhe].

Since software development projects typically contain lots of digital artifacts and various supporting systems such as Repositories, Issue Trackers and Wikis, searching and accessing this existing information is an important building block. Therefore, TeamWeaver [[Integrated Search]] allows to extract information from various software project data sources (e.g. SVN, CVS, Filesystem, Bugzilla, JIRA and various Wikis).
* Screencast: [http://www.teamweaver.org/downloads/media/screencasts/2008-10-30_integrated_search.avi TeamWeaver Integrated Search backend & browser-based client]

However, certain information - especially episodic "how-to" knowledge - might not be captured within an organization, or hidden on the local machines of certain developers. Therefore, TeamWeaver Integrated search can also be deployed as a kind of Eclipse-based Desktop Search Engine, to access local data of a developer.
* Screencast: [http://www.teamweaver.org/downloads/media/screencasts/2008-10-30_search_from_eclipse.avi Accessing a TeamWeaverIS server from within Eclipse]

On top of this infrastructure, the [[Inverse Search]] method tries to provide individual developers with clues which information is sought within an organization, and provides concrete recommendations on local documents which are worth sharing
* Screencast: [http://www.teamweaver.org/downloads/media/screencasts/2008-10-30_inverse_search.avi Inverse Search]

Finally, it can be useful for developers, to know which colleagues are experienced with a certain library, class or method. To this end, TeamWeaver monitors individual user's coding experience and allows them to share this with their colleagues. Embedded in the Eclipse coding help, developers can quickly recognize, which collegue is knowledgeable about a certain piece of code.
* Screencast: [http://www.teamweaver.org/downloads/media/screencasts/2008-10-22_reuse_experience_screencast.mov Eclipse Reuse Experience]

Here is also a copy of our flyer: [http://www.teamweaver.org/downloads/media/docs/2008-10-31_DemoCamp_Flyer.pdf TeamWeaver general information sheet]

[[Category:Event]]

Main Page

2009-06-17T09:22:05Z

ChristianRoehr:

<big>'''Welcome to the TeamWeaver Wiki!'''</big>

In their daily work, software engineers need efficient support for accessing project information and sharing personal experiences. TeamWeaver is an Open Source framework, which embeds lightweight and efficient knowledge access and sharing into the working context of a developer – realized for the Eclipse IDE.

Core features of TeamWeaver are Information access (search and assistance), need-driven knowledge sharing, automatic creating of context knowledge by user observation, lightweight "wiki-style" authoring and metadata storage with semantic technologies.

== [[News and Events]] ==
* 2009-06-03 At least 3 TeamWeaver developers will take part at the [http://wiki.eclipse.org/Eclipse_DemoCamps_Galileo_2009/Munich Eclipse Galileo DemoCamp in Munich ]
* 2009-05-18 A scientific study, which lays the work description feature (under development) was presented at the IEEE Inter. Conference on Mining Software repositories in Vancouver [http://msr.uwaterloo.ca/msr2009/msr09-schedule.pdf]
* 2009-03-26 The [[Woogle]] interface for TeamWeaver was presented at the 5th Conference on Professional Knowledge Management in Switzerland
See the [[News and Events | complete list]]

== Downloads ==
* We are currently offering three pre-bundled packages of software to try out:
** TeamWeaver [[Integrated Search]] - providing a server based search backend with a web-based frontend (Tomcat required for installation)
** TeamWeaver [[Wiquila]] - Prototype of our Swing-based Wiki Rich Client
** TeamWeaver [[Eureka]] Plugin for Eclipse (via Eclipse Update)

== Communication ==
You may want to subscribe to one of our TeamWeaver [[Mailinglists]].

== Source code ==
* TeamWeaver source code is kindly hosted by [http://www.polarion.com Polarion Software] at http://community.polarion.org
* Currently, you can check out TeamWeaver [[Wiquila]] and TeamWeaver [[Integrated Search]]. Further code will be moved there within the next weeks

== Aknowledgements ==
TeamWeaver development is funded by the European Commission within the project "[http://www.team-project.eu/ TEAM]" (IST 35111) and the German Federal Ministry of Education and Research within the project "[http://waves.fzi.de Waves]".

Partners contributing to TeamWeaver involve [http://www.fzi.de FZI Karlsruhe], [http://wwwbruegge.informatik.tu-muenchen.de/ Technische Universität München], [http://www.iccs.gr ICCS Greece] and [http://www.epfl.ch EPFL Lausanne].

We kindly thank [http://www.polarion.com Polarion Software] for offering us support and hosting.

== Contact ==
This page is hosted by [http://www.fzi.de/eng/contactform.html FZI Research Center for Information Technologies, Karlsruhe, Germany]. Contact for inquiries: Hans-Joerg Happel (lastname@fzi.de).

__NOTOC__