Share via


Performing a Basic Installation

Hh973130.collapse(en-us,VS.110).gifHh973130.expand(en-us,VS.110).gifHh973130.copycode(en-us,VS.110).gifHh973130.copycodeHighlight(en-us,VS.110).gifHh973130.drpdown(en-us,VS.110).gifHh973130.drpdown_orange(en-us,VS.110).gif

PreEmptive Analytics for TFS User Guide
Performing a Basic Installation
www.preemptive.com

Glossary Item Box

When performing a Basic installation, all components will be installed to the same machine (which must be running Microsoft Team Foundation Server). The PreEmptive Analytics Aggregator service will be installed and set to start automatically. A new database will be created in your local instance of SQL Server to store exception report data and a new website will be created in IIS to contain the PreEmptive Analytics endpoint message & query services (which receive exception report messages from instrumented applications and provide access to stored messages). The installation must be started by a user with administrative access to the local instance of SQL Server so that the new database can be deployed. You will be asked to provide credentials for a user account with permissions to create and edit work items in the local installation of Team Foundation Server. This account must also be able to log on to the local SQL Server installation, and will be used as the Application Pool identity for the new endpoint services applications created in IIS.

Aggregator Service Configuration

On this screen, specify the account name and password for an account that will be used to run the PreEmptive Analytics aggregator service and endpoint services. This account must have permissions to create and edit work items in the local installation of Team Foundation Server. Refer to the Team Foundation Server Administration Console to locate or create an account with these privileges. This account must also be able to log on to the local SQL Server installation, and will be used as the Application Pool identity for the new endpoint web service applications created in IIS. The installer will automatically assign this account the necessary rights to access the newly-created exceptions database and to host the endpoint web services.

Installation Complete

Upon successful installation, the installer will provide you with the URL of your exception message endpoint. You will need to provide this endpoint when using the Runtime Intelligence API or when instrumenting your applications for exception reporting with PreEmptive Dotfuscator or DashO. Instrumented applications must be able to access this endpoint, so you may need to adjust firewall settings to allow your target applications to send data to this endpoint. For more information about instrumenting your applications, see the Adding Exception Reporting to a .NET Application topic.

Once you close the installer, the PreEmptive Analytics configuration utility will launch to allow you to provision team projects for PreEmptive Analytics and to define rules and subscriptions to guide the creation of Incident work items. For more information, see the Configuring your Team Projects for PreEmptive Analytics topic.

Upload the PreEmptive Analytics visualizer extension for TFS Web Access (optional)

In order for users to view Incident work items in Team Foundation Server Web Access, a TFS administrator must upload and enable the PreEmptive Analytics visualizer extension. Follow the instructions in the Installing the Analytics Visualizer Extension for TFS Web Access topic to enable this functionality for your users.

See Also

Installing the Analytics Visualizer Extension for TFS Web Access

Configuring your Team Projects for PreEmptive Analytics
Configuring your Team Projects for PreEmptive Analytics

Adding Exception Reporting to a .NET Application
Adding Exception Reporting to a .NET Application

 

 

© 2012 PreEmptive Solutions. All rights reserved.