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,
IntroductionThe 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:
Supported Teamforge versions, user access requirements, other requirements
Anchor | ||||
---|---|---|---|---|
|
Step by step tutorial to crawl your first TeamForge
Anchor | ||||
---|---|---|---|---|
|
General instructions for crawling TeamForge with https
Anchor | ||||
---|---|---|---|---|
|
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