If you are installing Telligent Analytics 3.8, use your 3.7 license.

If you are a current Analytics 3.7 customer, Analytics 3.8 requires a full installation.

There is no upgrade path from Telligent Analytics 3.6 or below to Telligent Analytics 3.7 due to the restructuring of data and data tables in Telligent Community 6.0 and Telligent Enterprise 3.0.

The Installation Guide walks you through a full installation of Telligent Analytics. (You can also upgrade your installation.) After performing your installation, you can consult the Administrator's Guide for system tasks, or the User's Guide for user tasks.

System requirements

Your system must meet certain minimum requirements to successfully install Telligent Analytics. This document describes the software requirements, including:

Web server requirements

Microsoft operating systems do not ship with the Web server installed by default. If this is a clean installation of the operating system, the Web server must be installed and configured first and you must install and configure Internet Information Services (IIS). Telligent Analytics supports the following operating systems:

  • Windows Server 2003 with IIS 6 installed
  • Windows Server 2008 with IIS 7 installed

For testing and demonstration purposes, you can install Telligent Analytics on Windows XP with IIS 5.1 installed or Windows Vista with IIS 6 installed.

Development framework requirements

Microsoft .NET 4.0 must be installed on the server.

Tasks service requirements

The tasks services run on any Windows desktop/server operating system capable of running .NET Framework 4.0.

Database requirements

Telligent Analytics runs on either of the following database platforms:

  • Microsoft SQL Server 2005
  • Microsoft SQL Server 2008

For testing and demonstration purposes, you can use any Windows operating system that runs SQL Server 2005/2008.

If installing Telligent Analytics into a sub-directory, settings may be inherited from your parent application's web.config which cause a web.config error when you run your site. In such cases, you will have to add <clear /> or <remove /> elements in your Analytics web.config file to remove the additions made in your parent web.config.

Set up the Web server

  1. Create a Web directory folder and copy the files there. 
    1. Create a path to hold the Telligent Analytics files (e.g., D:\TelligentAnalytics\Web\).
    2. In the extracted .zip file folder, copy all of the file's Web folder contents and paste them into the new Web directory folder, leaving the directory structure intact.
  2. Create a new application pool. (If using Windows XP for development purposes, skip this step.)
    These instructions assume you're running IIS7. If you’re using IIS6, see the Microsoft documentation.

    1. Open Internet Information Services (IIS) Manager.
    2. If required, connect to your Web server.
    3. In the Connections pane on the right, expand your Web server.
    4. Right-click Application Pools and select Add Application Pool.
    5. Specify a name for your application pool.
    6. Ensure that the .Net framework version selected is v.4.0.x.
      To ensure that your IIS instance is configured to run ASP.NET applications in Windows Server 2008, find this information under application development in Role Services.
    7. Click OK.

  3. Create the IIS application.
    1. In IIS's left pane, navigate to Internet Information Services > [computer name] > Web Sites > Default Web Site.
    2. Right-click Default Web Site, select New from the menu, then select Add Application.

    3. Do the following in the Add Application window:
      • Enter a name in the alias field (e.g., Telligent Analytics).
      • Enter the path you created in Step 1 in the Physical path field (e.g., D:\TelligentAnalytics\Web).
      • Ensure that the selected application pool is the same one you created in Step 2.
    4. Click OK in Add Application window.
  4. Determine your Web site service account. This account will be needed for granting permissions in the next step and in the Database section.
    • If using Windows XP for development purposes, your service account is ASPNET.
    • If using Windows Server 2003 or Window Server 2003 R2, your service account is NETWORK SERVICE.
    • If using Windows Server 2008, Vista or higher, follow these steps to find the service account under which your Web service is running:
      1. Open IIS Manager and navigate to Application Pools.
      2. Use the value of the identity column to determine your Web site service account:
        • LocalService - NT AUTHORITY\LOCAL SERVICE
        • LocalSystem - NT AUTHORITY\SYSTEM
        • NetworkService - NT AUTHORITY\NETWORK SERVICE
        • ApplicationPoolIdentity - IIS APPPOOL\ <app pool name>
        • OTHER - runs as the specified user

  5. Grant the Web site service account read permissions to the Web site.
    1. Right-click the Telligent Analytics Web site folder and select Properties.
    2. Click the Security tab. (If you are using Windows Server 2008 and above or Windows Vista and above, click Edit.)
    3. Click Add.

    4. In the Enter the object names text box, type the name of the service account determined in Step 4 above and click Check Names. After the name resolves, click OK.
      If you are using IIS6, you will also need to grant permissions to the account IUSR_{YOURCOMPUTERNAME} for the IIS user account. The best way to find the IUSR user you need is to get to this point, then click Advanced. In the dialog window that appears, click Find Now to see all of the available accounts. Look for the account that starts with "IUSR_" and is followed by the name of your computer. If you do not see any accounts that match, you may need to change the "From this location" field to something different (e.g., from a work network to your personal computer). If you are using Windows XP, repeat this process for the ASPNET account.
    5. Ensure that the service account is selected in the top pane, and view the bottom Permissions pane to ensure that only the Read permission is granted.

    6. Click OK. (If you are using Windows Server 2008 and higher or Vista and higher OS, click OK a second time.)

Set up the database

The collation case sensitivity setting of your Telligent Analytics database must match the collation case sensitivity setting of your Telligent Evolution database, which should default to being case-insensitive. (The only collation setting that Telligent Evolution supports is SQL_Latin1_General_CP1_CI_AS). You can find the case sensitivity setting at [database name] > Properties > Options > Collation.
  1. Create a new database in SQL Server.
    1. Open SQL Server Management Studio and connect to your database server with an account that has sysadmin or dbcreator fixed server privileges.
    2. Right-click Databases and select New Database. The New Database window appears.

    3. In the Database name field, enter a name for the database. (Example: Telligent Analytics.)

    4. In the Select a Page pane on the left, select Options.
    5. Make sure that Recovery Model is set to Simple.
    6. Click OK.
      We recommend you run this database in simple recovery mode because it requires less disk space.
  2. Populate the database by executing the TelligentAnalytics_Install.sql script from the \SQL\ folder of the install package.
    1. In SQL Server Management Studio, navigate to File > Open > File. The Open File dialog window appears.
    2. Navigate to the temporary location where you unzipped the installation package and within that folder, to SQL.
    3. Double-click TelligentAnalytics_Install.sql.
    4. Select the database you created in Step 1.

    5. Execute the query against the database.
  3. Create a login for Telligent Analytics to use for accessing the database.
    1. In SQL Server's Object Explorer pane on the left-hand side, expand the Security folder, then right-click Logins and select Add new login.

    2. If you want Telligent Analytics to connect to the database via Windows Authentication, select General and then specify the login name as the username of the service account user determined above. If you want Telligent Analytics to connect to the database using SQL authentication, then specify any username in the Login name text box. Click OK.
      We recommend using Windows Authentication. If you want to use SQL authentication, make sure your SQL server supports mixed-mode authentication.
    3. Click OK.
  4. Grant the login access to the Telligent Analytics database.
    1. In the Object Explorer, expand your database, expand Security, right-click Users, and select New User.

    2. In the User name and Login name fields, enter the name of the login you created in Set up the Web Server Step 4.

    3. In the bottom (Database role membership) pane, ensure the db_owner role is checked.
    4. Click OK.

Connect Web site to the database

  1. Update connectionstrings.config in the Web site to point to your new database.
    1. Open the connectionstrings.config file in your Web folder, and update the HRSDB entry to point to the database you created above.
    2. If using Windows Authentication to connect to the database, the connection string should look something like:

      <add name="HRSDB"
        connectionString="server=SERVERNAME;database=DATABASENAME;Trusted_Connection=yes;" 
        />
      
    3. If using SQL authentication, the connection string should look something like:

      <add name="HRSDB" 
        connectionString="server=SERVERNAME;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=no;"
        />
      
    4. If you're using SQL Express for development purposes, the SERVERNAME in the connection string may be (local)\SQLExpress as opposed to just (local).

      <add name="HRSDB"
        connectionString="server=(local)\SQLExpress;database=DATABASENAME;Trusted_Connection=yes;"
        />
      <add name="HRSDB"
        connectionString="server=(local)\SQLExpress;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=yes;"
        />
      

Configure Telligent Analytics Web settings

If you plan on using Shared Membership or Windows Authentication to authenticate against Telligent Analytics, configure these now.

  1. If not using Shared Membership or Windows Authentication, change your administrator password in the web.config file.
    1. In the folder you installed the Telligent Analytics Web site, open the web.config file.
    2. Find the line that reads
      <user name="admin" password="1.pa$$w0rd" />
      and change the value of the password, e.g.,
      <user name="admin" password="N£w Pa$$w0rd" />
  2. Install your license.
    1. Navigate to your Web site.
    2. Click Settings on the navigation bar in the top-right corner.
    3. If asked to log in, enter your credentials.
    4. Select Site Options from the administrative task list. The General Settings page appears.

    5. Scroll down to the Licenses section.
    6. Browse to the license file emailed to you by Telligent Support (license.xml) file and click Upload. You will receive a message that the installation is successful.
    7. Click OK.
  3. Create a site in the application for each community on which you want to report.
    1. From the Control Panel, click Manage Sites on the left bar.

    2. Fill out the form on this page to create a site in Telligent Analytics:
      1. Site Name - Enter a name for your site. This name will identify the site in Telligent Analytics.
      2. Site URL - Enter the actual URL for your community site. This will be used to create external links to actual content in your community.
      3. Schema Name - Enter a database schema name to be used to store tables and data in the Telligent Analytics database for this site. This schema may not currently be in use by any other Telligent Analytics sites. If the schema name you specify here does not yet exist, Telligent Analytics will create it. For your first site, we recommend community since this is the default schema defined in the preconfigured task files.
      4. Package - To to utilize our out-of-the-box reports for Telligent Community / Enterprise, select Telligent Community/ Enterprise Reports. You can optionally create your own reports package, and utilize it by creating a site the same way.
    3. Repeat this process for each Telligent Evolution community on which you want to report.

Set up Web Analytics (Extended Analytics)

If you are using IIS6 instead of IIS7, there are some differences to be aware of. This article details some critical differences.
  1. In the [Telligent Evolution Site]>\Web.config file, locate the <modules> section in <system.webServer>.Uncomment the JavascriptAnalyticsHttpModule module line. If you are running IIS6, also move JavascriptAnalyticsHttpModule to the <system.web><httpModules> section.
  2. Locate the <handlers> section, and uncomment the analytics and analyticsUrls handlers. If you are running IIS6, also move these handlers to the <system.web><httpHandlers> section.
  3. Optional: If your Telligent Enterprise site is running in a Web farm, make sure steps 1 and 2 happen on all Web servers.

    If you want to check on the progress of this import (or to validate that data is being imported), see Validating installation. If data hasn't imported after a certain time, see the appropriate troubleshooting article.
If you are using these instructions to install 3.7 for use with an existing 3.6 or earlier database, be sure to refer to the 3.7 upgrade FAQ for information.

Install Anaytics Task Runner

With Telligent Analytics 3.7 and 3.8, the preferred method of setting up tasks is to use the Analytics Task Runner. Please note: You cannot install both the Task Runner and the Task Service.

  1. Ensure your environment follows the recommended hardware and hosting guidelines.
  2. Ensure Telligent Analytics 3.7 or 3.8 is correctly installed following the instructions above.
  3. The Analytics Runner exe will be scheduled to run using a Scheduled Task. This task will need credentials or an account to run as, for best results its recommended that you use a domain account that either is dedicated to Analytics, or dedicated to running “services.”
  4. You will need one or more accounts with database access to run analytics runner. The specific instructions differ based upon which authentication mechanism your site is using. If you’re not sure about this ask your database or network administrator.
    • Database Windows Authentication: If your database uses windows authentication you will need one single domain account that has the appropriate levels of access to all of the databases listed in your connectionstrings.config.
    • Database SQL Authentication: If your database uses SQL authentication, you will need to set up SQL authentication by editing the connectionStrings.config and supplying the correct accounts to each of the connection strings.
  5. If you have the task service already installed from a previous Telligent Analytics version, you will need to uninstall the task service. Locate the Telligent Analytics tasks directory. Run the uninstallservice.bat file located in the Tasks directory to uninstall the Telligent Analytics Task Service.
  6. Make sure that the connectionStrings.config file in the Tasks folder is update with the correct connection strings to both the Telligent Community (or Telligent Enterprise) databases, as well as the Telligent Analytics databases.
  7. If you used a schema name other than "community", make sure to update the TaskStrings.config file Sites\siteSchema value.
  8. Start Tasks\AnalyticsRunner.exe from a command line to ensure that it works, and is configured correctly. Once you verify that it is working correctly you can move to the next step.
  9. Review the Scheduled Task documentation to familiarize yourself with the Scheduled Task system in Microsoft Windows.
  10. Give the task a name, for this document we will assume that the name is “Telligent Analytics Runner.”
  11. Give the task a description, but not overly long. Include any specific notes that other admins or personnel might need to understand.
  12. Specify the account that will run the task. Select run as Run Whether User Is Logged On Or Not.
  13. Create a new Trigger, Settings: Daily, Start (today’s date) at 1:00:00AM. Recur every 1 days. Leave all other defaults unchanged.
  14. Create a new Action, Start a Program. Browse to the location of Analytics Runner that you set up previously.
  15. If given the option to supply a "Start in" value, enter the location of the folder the AnalyticsRunner.exe resides in.
  16. Select “Run task as soon as possible after a scheduled start is missed”. Click OK to save your task.
  17. It's recommended that AnalyticsRunner runs once per day. Depending upon the size of your community, and the size of your hardware, it may be possible to run it more than once per day. If you wish to do this please carefully monitor the task to see how long it is taking before opting to have it run more than once per day.

Install Tasks Service

Please note that this is no longer the recommended way to enable Telligent Analytics tasks. Please see Install Analytics Task Runner. Please note: You cannot install both the Task Runner and the Tasks Service.

  1. Create a Tasks Service directory and copy the files there:
    1. Create a directory to hold the Telligent Analytics Tasks site (e.g., D:\TelligentAnalytics\Tasks\).
    2. From the extracted .zip file folder, copy the contents of the Tasks folder and paste them into the directory created above.
  2. Update the connection strings to point to your database:
    1. Open up connectionStrings.config in a text editor (e.g., Notepad).
    2. Modify the entries as follows:
      • Community1 - This should be the connection string to your Telligent Evolution community database.
      • Community1SharedMembership - If your community uses shared membership, this should point to your shared membership database; otherwise it should be the same as your Community1 connection string.
      • Community1Reporting - This should be the connection string to your Telligent Analytics database.
      • HRSDB - This should be the connection string to your Telligent Analytics database.
    3. If you added more than one site through Settings > Manage Sites, you'll need to add entries in the connectionStrings.config for each extra site, labeling them as "Community2", "Community2SharedMembership", "Community2Reporting", etc.
  3. Update the task strings (skip this step if you only have one site):
    1. Open up taskStrings.configin a text editor (e.g., Notepad).
      <?xml version="1.0" encoding="utf-8" ?>
      <Tasks>
        <BulkCopyRowCounter value="1" />
        <!-- DECLARE SITES -->
        <Sites>
          <!-- add additional Site entries to have Tasks 
              Assign Connection String Aliases to Sources.
              Aliases should reference Connection Strings
          <Site name="Community1"
            Community = "Community1"
            Membership = "Community1SharedMembership"
            Reporting = "Community1Reporting"
            WebAnalytics = "Community1WebAnalytics"
            siteSchema = "community" />
        </Sites>
      
    2. Add a new <site> node in the <Sites> section for each site and set the attribute values to match those from the connectionstrings.config file.
    3. Change the SiteSchema property to match the schema entered when you created each new site through Settings > Manage Sites.
  4. Generate a Flickr application key and a Bing application:
    1. If you want to use third-party sites for pulling external buzz. In release 3.7, users are not registered to these sites, only to Twitter.
      1. Generate a Flickr application key at http://www.flickr.services/apps/create and follow the onscreen instructions.
      2. Generate a Bing application ID at http://www.bing.com/developers/createapp.aspx and follow the onscreen instructions.
  5. Configure Tasks Service:
    1. Open up Telligent.Tasks.Service.exe.config.
    2. Configure Buzz:
      1. Find the <AppSettings> element.
      2. Set the FlickAPIKey to the value of the Flickr API key you generated above.
      3. Set the LiveAppKey to the value of the Bing application ID you generated above.
      4. Configure email:
        1. Find the <system.net> element. Update the smtpfrom address from noreply@yourdomain.com to the email address used to send outgoing mail. You may need to contact a network administrator for an appropriate outgoing email address.
        2. Modify the host attribute on the network element to be the name or IP address of your mail server.
  6. Install the service:
    1. Open a command prompt as an administrator.
    2. Execute the installService.bat file in the Tasks directory. For example, execute the following from the command line:

      D:\TelligentAnalytics\Tasks\installService.bat
    3. Note that when you install the Tasks Service, if you do not run the install file from the command prompt and as an administrator, you can receive an installation error stating that your security logs are inaccessible.
  7. Optionally, if you want to install the task service on a separate server:
    1. Open Windows Services (Control Panel > Services).
    2. Right-click the Telligent Task Service and select Properties.
    3. In the General tab, keep the startup type as Automatic so that the task will always restart after a reboot. Or if you are running Windows Vista/Server 2008+, change the startup type to Automatic (Delayed Start).
    4. In the Log On tab, select the Log on as setting for this account.
    5. Click Browse. In the dialog box, ensure that you have selected the correct Object Type (Built-in security principals, Users); Location (the computer/server you're accessing), and the Object name (remains the same, e.g., Network Service).
    6. Click OK.
  8. Start the service:
    1. Go to Start > Run, type in services.msc and press OK.
    2. In the Services List, find the entry for "Telligent Analytics Task Service," right-click it, and select Start.

You will not see data in your Telligent Analytics site sooner than one hour from when the task service is installed. Most likely, it will take longer.