You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Welcome to TeamForge for Aspire. A central location for all information on crawling and processing content using the Aspire TeamForge connector and associated components.

 

On this page:

Related pages:

 

Introduction

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:

  • Ability to perform either full or incremental crawling (so that only new/updated documents are indexed)
  • Fetches access control lists (ACLs) for TeamForge item-level security (Security is based on TeamForge users, groups and roles)
  • Fetches metadata for retrieved content
  • Is search engine independent. The content retrieved can be published by Aspire to any search engine
  • Runs from any server with access to the given TeamForge repository and conforms to the Hardware and Network Considerations for Aspire .

Future Development Plan

  • Ability to control what content is requested from the repository during crawling.

Prerequisites 

Supported Teamforge versions, user access requirements, other requirements

How to configure

Step by step tutorial to crawl your first TeamForge

 General instructions for crawling TeamForge with https

FAQ & Troubleshooting

Why is does an incremental crawl last as long as a full crawl?

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

Save your content source before creating or editing another one

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.

Developer Information

 This section is for advanced topics and information mostly for programmers who wish to work with the TeamForge App Bundle or the TeamForge scanner.

TeamForge Application Bundle 

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.

TeamForge Scanner

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.

TeamForge Group Expansion

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.

TeamForge Fecth Url

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.

TeamForge SOAP Services

 Detailed information on supporting SOAP services, items and item fields.

TeamForge concerning information 

  • No labels