Installing the Combined Endpoint and Aggregator Role

Hh973138.copycode(en-us,VS.110).gif Hh973138.copycodeHighlight(en-us,VS.110).gif Hh973138.drpdown(en-us,VS.110).gif Hh973138.drpdown_orange(en-us,VS.110).gif

PreEmptive Analytics for TFS User Guide
Installing the Combined Endpoint and Aggregator Role
www.preemptive.com

Glossary Item Box

When installing the Combined Exception Endpoint & Aggregator Role, all components will be installed to the same machine. The PreEmptive Analytics Aggregator service will be installed and set to start automatically. 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. A new database will be created in an 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 target instance of SQL Server so that the new database can be deployed. You will be asked to provide account credentials to be used as the Application Pool identity for the new endpoint services applications created in IIS, and you will choose whether to also use this account for Integrated Security authentication to the target instance of SQL Server, or whether to provide a login and password for use with SQL Authentication.

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. You may also choose to specify the location on disk into which the PreEmptive Analytics program files will be installed, or you may leave the default selection.

Exception Endpoint IIS Configuration

On this screen, you must specify the account name and password to be used as the IIS Application Pool identity for the PreEmptive Analytics endpoint services. If you choose to use Integrated Security for communication between the endpoint services and SQL Server, this account will also be granted permissions to log on to the target instance of SQL Server.

Next, you may specify the name of the IIS Application Pool that will be used to host the endpoint services and select the IIS Website into which the PreEmptive Analytics endpoint services will be installed. If the website already exists, the endpoint services applications will be added to the root of the website and its port binding will not be modified. If the website does not exist, it will be created and a binding will be added to listen on the port specified.

Exception Endpoint SQL Configuration

On this screen, you may specify the hostname of the SQL Server instance in which a new database will be created to store exception report message data. You may also specify the name of the database to be used. Ensure that there is not an existing database with the same name on the selected instance of SQL Server.

Next, decide whether Integrated Security or SQL Authentication should be used for communication between the endpoint services and the SQL Server database. If using Integrated Security, the IIS Application Pool user account specified in the Exception Endpoint IIS Configuration screen will be used. Depending on your choice, the installer will create a new Integrated Security or SQL Authentication login on the target SQL Server instance if one does not exist, and the specified login will be granted permission to use the newly-created database.

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.