Welcome to TeamForge for Aspire. A central location for all information on crawling and processing content using the Aspire TeamForge connector and associated components.
Status subtle true colour Yellow title This item is being deprecated.
About the TeamForge connector for Aspire, how it works, features,
Supported Teamforge versions, user access requirements, other requirements
The TeamForge connector will crawl content from TeamForge repository server through its SOAP services. The connector will request and retrieve items related to TeamForge project, discussion, document, release, news, project page, planning folder, repositorie, task, tracker and wiki services.
Note that the TeamForge connector is not part of Aspire Community bundle, but may be purchased separately
Some of the features of the TeamForge connector include:
The Aspire TeamForge connector was created and tested using a TeamForge repository version 7.0.0.1.380 and 6.1.0.0.353 with SOAP API.
Before installing the TeamForge Connector, make sure that:
You will need the user login later, as part of installing the TeamForge Connector.
The Aspire TeamForge connector can run on either Windows or Linux. It uses the TeamForge's SOAP API to communicate with TeamForge repository.
The TeamForge API services should be started and running automatically if TeamForge is up and running. These are required for the Aspire TeamForge Connector to successfully connect with the TeamForge docbase that you want to index.
Anchor | ||||
---|---|---|---|---|
|
Step by step tutorial to crawl your first TeamForge
Anchor | ||||
---|---|---|---|---|
|
General instructions for crawling TeamForge with https
Anchor | ||||
---|---|---|---|---|
|
The TeamForge Connector performs incremental crawls based on snapshot files, which are meant to match the exact documents that have been indexed by the connector to the search engine. On an incremental crawl the connector fully crawls the TeamForge content the same way as a full crawl, but it only indexes the modified, new or deleted documents during that crawl.
For a discussion on crawling, see here
Failing to save a content source before creating or editing another content source can result in an error.
ERROR [aspire]: Exception received attempting to get execute component command com.searchtechnologies.aspire.services.AspireException: Unable to find content source
Save the initial content source before creating or working on another.
Questions and answers, including troubleshooting techniques
Anchor | ||||
---|---|---|---|---|
|
This section is for advanced topics and information mostly for programmers who wish to work with the TeamForge App Bundle or the TeamForge scanner.
Detailed information on configuring the TeamForge App Bundle. Also includes a discussion of all of the metadata produced by the App Bundle, with an example.
Detailed information on the TeamForge java component which scans for TeamForge content. Only needed by programmers who might need to integrate the TeamForge scanner in novel ways not supported by the standard framework and routing table.
Detailed information on configuring the TeamForge group expansion component. This is bundled with the TeamForge connector, so this information on the component is only needed by programmers who might have custom TeamForge integration needs.
Detailed information on the TeamForge Fetch Url java component which opens an InputStream to the given URL which can be read by down-stream pipeline stages. Only needed by programmers who might need to integrate the TeamForge scanner in novel ways not supported by the standard framework and routing table.
Detailed information on supporting SOAP services, items and item fields.
TeamForge concerning information