Telligent Analytics

Wiki: Telligent Analytics Product Documentation

Anonymous — Tue, 31 Jan 2012 22:04:00 GMT

Guides for administrators and users of Telligent Analytics

Wiki Page: Tasks

Jenny Jarrard — Tue, 31 Jan 2012 16:04:00 GMT

In Release 3.5, Telligent Analytics added ancillary data caching for faster page views and improved User Agent parsing.

This section contains the following information about tasks:

Wiki Page: About Web Analytics (3.5)

Jenny Jarrard — Tue, 31 Jan 2012 15:59:00 GMT

In Release 3.6 and 3.7, new Web Analytics were shipped.

In Release 3.5: Telligent Analytics makes use of page views to more accurately reflect true page views for actual user visits, filtering out requests from page view totals including response codes other than 200; robot/crawler visits, and requests from within Telligent Evolution itself.

Pre-calculated roll-up data is used for page views as well as topics and sentiment.

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this approach differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

Web Analytics is the collection, analysis, and reporting of information about Internet traffic on your Web site. Telligent Analytics 3.0 introduces all three stages of this process for use with your Telligent Evolution site.

How is data collected?

Telligent Analytics 3.0 includes an additional assembly (ExtendedAnalytics.dll) that runs on your community site to collect traffic information. This assembly includes an HttpModule that subscribes to the End Request event of every page request, then records detailed information about each request made to the community site.

This module uses an additional user cookie for tracking unique users and returning visitors. If a user logs in, the cookie is tied directly to his/her site membership account - adding the ability to report on views by specific community members.

The Analytics module requires additional tables and stored procedures to be added to your community site. The script for adding these elements, as well as the assembly file and other configuration files, is found in the ExtendedAnaltyics folder of your Telligent Analytics 3.0 installation package. Follow the Analytics 3.0 installation instructions for more information on adding the module to your community site.

The module includes a configurable queue which collects requests. These requests are then written to the database in bulk. The ExtendedAnalytics.config file allows you to specify how often these items are written to the database. If necessary, the files can be written to a separate database. For larger communities, it is recommended the requests be frequently written out and that they be stored in a separate database.

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: dynamicstyle.aspx)
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this approach differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

These approaches are typical because a tool built on one or both of these technologies can be applied to a large customer base regardless of the server type or Web application type being run (e.g., HTML, PHP, ASP.NET, etc.).

Some drawbacks of these technologies:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers.
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Because Telligent Analytics targets a specific technology and specific application, we are able to leverage technologies specific to ASP.NET and information specific to Telligent platforms that allow access to more precise information about each request. For example, because we integrate the ExtendedAnalytics module directly with the Telligent platform application, we are able to record additional information about each request by:

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community/context-specific information about the page requested (i.e., Which community group, section, and post(s) are associated with the page?)

The statistics gathered by each different method of collecting Web Analytics statistics can vary greatly. We selected an HttpModule approach because the limited scope of this solution allows us greater control over each request - and ultimately results in greater accuracy.

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although, note, it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the cleanup job (see CleanupJob.sql) be installed to delete old records and free storage space.

How is the data analyzed?

Requests are imported into the Analytics database through the WebAnalyticsTask. This unique task processes requests and organizes requests based on user and session information. Information about individual views, statistics on page requests, and browser and referrer information are also processed as part of this task.

The WebAnalyticsTask differentiates between browser views, RSS views, and robot or crawler views; it then stores each of these types separately in the Analytics database for reporting. The primary means of differentiating between these types is through intelligent parsing of the Http User Agent string passed with the request.

In the directory where you install the Telligent Analytics 3.0 tasks, there is a configuration file named WebAnalytics.config. This holds the current list of regular expressions used to identify common user agent strings, broken out by category. It may be necessary to update this file periodically as new user agents are introduced. Check the Telligent Web site periodically for published updates to this file.

The Web Analytics task is intended to be run frequently. Out of the box, this task is configured to run once every hour. The resulting reports in Telligent Analytics will be close to real-time (only off by at most one hour). The interval between executions is also configurable.

What reports are included?

Telligent Analytics 3.0 includes a comprehensive set of reports built around views, visitors, pages, and referrers. Here is a list of the different sections of reports included with Telligent Analytics 3.0:

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

Wiki Page: 1. Full installation for release 3.7

Jenny Jarrard — Wed, 18 Jan 2012 19:03:00 GMT

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

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.
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.
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.
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
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

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.
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.
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.
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

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.

If not using Shared Membership or Windows Authentication, change your administrator password in the web.configfile.
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" />
```
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.
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)

In the [Telligent Evolution Site]>\Web.config file, locate the <modules> section in <system.webServer>. Uncomment the JavascriptAnalyticsHttpModule module line.
Locate the <handlers> section, and uncomment the analytics and analyticsUrls handlers.
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 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, 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.

Ensure your environment follows the recommended hardware and hosting guidelines.
Ensure Telligent Analytics 3.7 is correctly installed following the instructions above.
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.”
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.
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.
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.
If you used a schema name other than "community", make sure to update the TaskStrings.config file Sites\siteSchema value.
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.
Review the Scheduled Task documentation to familiarize yourself with the Scheduled Task system in Microsoft Windows.
Give the task a name, for this document we will assume that the name is “Telligent Analytics Runner.”
Give the task a description, but not overly long. Include any specific notes that other admins or personnel might need to understand.
Specify the account that will run the task. Select run as Run Whether User Is Logged On Or Not.
Create a new Trigger, Settings: Daily, Start (today’s date) at 1:00:00AM. Recur every 1 days. Leave all other defaults unchanged.
Create a new Action, Start a Program. Browse to the location of Analytics Runner that you set up previously.
Select “Run task as soon as possible after a scheduled start is missed”. Click OK to save your task.
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.

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.
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.

Update the task strings (skip this step if you only have one site):

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>

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.
Change the SiteSchema property to match the schema entered when you created each new site through Settings > Manage Sites.

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.
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.
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.
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.
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.

Forum Post: RE: Telligent 3.6 bin directory

Jayme Davis — Mon, 12 Dec 2011 18:08:00 GMT

The config files are necessary. The .xml files, images/template directories can be removed.

Forum Post: RE: Object Reference not set to an object when clicking Web Analytics

JanaCarter [Telligent] — Tue, 06 Dec 2011 19:49:00 GMT

I have a few questions for you to gather additional information:

1. Do you only receive this error when clicking on the Web Analytics tab? Do you get this error if you click on the other tabs (Users, Buzz, Collaboration)?

2. Has this tab ever loaded?

3. Can you navigate directly to a report on the Web Analtyis tab and does it load? To do this, use the search box and search for "Page Views" and click one of the results. Let me know if that loads for you.

4. Do you know if any "new groups" were recently added to your community?

5. Any configuration changes made recently?

Thank you

Jana Carter

Telligent Analytics Program Manager

Forum Post: RE: Anonymous Visitors for Private Groups

JanaCarter [Telligent] — Tue, 22 Nov 2011 21:12:00 GMT

Jenney:

Can I assume you are using Windows Authentication for your Community site? If yes, then that would explain the "anonymous visitors" in a private group. We recently provided a hotfix to correct this issue. I noticed you are on the first release of 3.6. We have had several hotfixes since this release. I can provide you with the hotfix that will correct this issue (as well as provide you some fixes for other important items).

Let me know.

Thank you

Jana

Forum Post: RE: limit analytics child app to the community adminsitrators group

Jayme Davis — Tue, 22 Nov 2011 20:12:00 GMT

You will need to setup shared membership for this to work: telligent.com/.../setting-up-shared-membership.aspx

Forum Post: RE: Errors while trying to set up first time.

Billy — Tue, 22 Nov 2011 00:51:00 GMT

I redid both analytics databases and put community in the schema name and now am waiting to see if I will get data again. I think that i should be getting data again since i actually had some data before.

Wiki Page: 1. Full installation through release 3.6

Michael Kelley — Mon, 21 Nov 2011 21:29:00 GMT

System requirements

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

Web server requirements

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 3.5 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 3.5.

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.

Set up the Web server

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 zip file's web folder contents and paste them into the new Web directory folder, leaving the directory structure intact.
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 versionselected is v.2.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.
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.
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
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

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 displays.
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.
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 displays.
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.
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.
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

Update connectionstrings.config in the Web site to point to your new database.

Open the connectionstrings.config file in your Web folder, and update the HRSDB entry to point to the database you created above.

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;" 
  />

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;"
  />

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.

If not using Shared Membership or Windows Authentication, change your administrator password in the web.configfile.
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" />
```
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 displays.
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.
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.
    
    The Schema Name must match what is identified in the taskstrings.config file (line 15, siteSchema = "community" />). A good rule of thumb is to double-check that both places match exactly. Note: When updating the Schema Name in Telligent Analytics > Settings > Manage Sites, the label will change to read "User Schema." User Schema is the same as Schema Name.
  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)

Upgrade

For those currently running 3.5. (If you're not upgrading, jump to the Install instructions below.)

[IIS6.0 or IIS7.0 in Non-Integrated Mode]

Remove the following element from <httpModules> section of <system.web>

<add name="PageAnalyticsHttpModule" type="CommunityServer.ExtendedAnalytics.PageAnalyticsHttpModule, CommunityServer.ExtendedAnalytics" />

[IIS7.0]

Remove any of the following elements from the <modules> section in <system.webServer>:

<remove name="PageAnalyticsHttpModule"/>
<add name="PageAnalyticsHttpModule" preCondition="managedHandler" type="CommunityServer.ExtendedAnalytics.PageAnalyticsHttpModule, CommunityServer.ExtendedAnalytics"/></modules>

Install

For all users, including upgrade users:

Run the ExtendedAnalytics.sql file on your Telligent Evolution database or other database if you prefer.
Copy CommunityServer.ExtendedAnalytics.dll (see Assembly folder) to the [Telligent Evolution site]\bin directory.
Copy the configuration file ExtendedAnalytics.config to the [Telligent Evolution site] directory (same folder as the Web.config).
1. If you use a different database from your Telligent Evolution database to store your Web analytics, then set the "UseDefaultConnectionString" setting to 0 and set the "CustomConnectionString" setting to work with the database.

Register the 'JavascriptAnalyticsHttpModule' http module in [Telligent Evolution site]\Web.config. Note: Register it after all the other modules.

[IIS6.0 or IIS7.0 in Non-Integrated Mode]

Add this to the <httpModules> section of <system.web>:

<add name="JavascriptAnalyticsHttpModule" type="CommunityServer.ExtendedAnalytics.JavascriptAnalyticsHttpModule, CommunityServer.ExtendedAnalytics" />

[IIS7.0]

Add this to <modules> section of <system.webServer>:

<remove name="JavascriptAnalyticsHttpModule"/>
<add name="JavascriptAnalyticsHttpModule" type="CommunityServer.ExtendedAnalytics.JavascriptAnalyticsHttpModule, CommunityServer.ExtendedAnalytics"/>

Register the 'ExtendedAnalyticsRequestHandler' http handler in [Telligent Evolution site]\Web.config.

[IIS6.0 or IIS7.0 in Non-Integrated Mode]
Add this to <httpHandlers> section of <system.web>:

<add verb="GET" path="analytics.ashx" type="CommunityServer.ExtendedAnalytics.ExtendedAnalyticsRequestHandler, CommunityServer.ExtendedAnalytics"/>

[IIS7.0]
Add this to <handlers> in <system.webServer>:

<remove name="ExtendedAnalyticsRequestHandler"/>
<add name="ExtendedAnalyticsRequestHandler" verb="GET" path="analytics.ashx" type="CommunityServer.ExtendedAnalytics.ExtendedAnalyticsRequestHandler, CommunityServer.ExtendedAnalytics"/>

Optional: If your Telligent Evolution site is running in a Web farm, make sure steps 3, 4, and 5 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.

Install Tasks Service

Create a Tasks Service directory and copy the files there:
1. Create a directory to hold the Telligent Analytics Tasks Service (e.g., D:\TelligentAnalytics\Tasks\).
2. From the extracted .zip file folder, copy the contents of the Tasks folder contents and paste them into the directory created above.
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.configfor each extra site, labeling them as "Community2", "Community2SharedMembership", "Community2Reporting", etc.

Update the task strings (skip this step if you only have one site):

Open up taskStrings.config in 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>

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.
Change the SiteSchema property to match the schema entered when you created each new site through Settings > Manage Sites.

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.6, users are not registered to these sites by default, only to Twitter.
  - Generate a Flickr Application Key at http://www.flickr.com/services/apps/create/ and follow the onscreen instructions.
  - Generate a Bing Application ID at http://www.bing.com/developers/createapp.aspx and follow the onscreen instructions.
Configure Tasks Service:
1. Open up Telligent.Tasks.Service.exe.config.
2. Configure Buzz:
  1. Find the <AppSettings> Element.
  2. Set the FlickrAPIKey to the value of the FlickrAPI Key you generated above.
  3. Set the LiveAppKey to the value of the Bing Application ID you generated above.
3. Configure email:
  1. Find the <system.net> element.
  2. 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.
  3. Modify the host attribute on the network element to be the name or IP address of your mail server.
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
```
Note that when you install the Tasks Service, if you do not run the install file from the command prompt and as administrator, you can receive an installation error stating that your security logs are inaccessible.
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.
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.

Wiki Page: 3.7 upgrade FAQ

Jenny Jarrard — Wed, 16 Nov 2011 19:28:00 GMT

If you are upgrading from Telligent Analytics 3.x to Analytics 3.7, please read the below, then follow the full installation instructions.

Which versions of Telligent Evolution are compatible with Telligent Analytics 3.7?

Telligent Analytics 3.7 is compatible with Telligent Community 6.0 and Telligent Enterprise 3.0. It is not compatible with down-level versions of the Telligent Evolution platform.

If you have upgraded to Telligent Community 6.0 or Telligent Enterprise 3.0, please verify that the cs_UpdateSchemaAndProcedures.sql script was executed and that your upgrade completely successfully.

Telligent Analytics 3.6 is not compatible with Telligent Community 6.0 and Telligent Enterprise 3.0.

How do I upgrade from an older version of Telligent Analytics to Telligent Analytics 3.7?

Please follow the full installation instructions. Most of the document is written from the standpoint of moving from Telligent Analytics 3.6 to 3.7.

Why a new install?

There has been major restructuring of data and data tables in Telligent Community 6.0 and Telligent Enterprise 3.0. This required upgrades to be made to our Telligent Analytics product. 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.

Upgrade web analytics data

One restructuring that took place in Telligent Community 6.0 and Telligent Enterprise 3.0 was in the way that web analytics data was stored in the database. What this means for Telligent Analytics is that the older legacy data will need to be upgraded if you wish to report that data upon going forward. Telligent Analytics 3.7 ships with a database script to migrate the web analytics data. This is a script that you run on your Telligent Community 6.0 or Telligent Enterprise 3.0 database, not on the Telligent Analytics 3.7 database. You can run this script before or after you get Telligent Analytics set up. Bear in mind, though, if you choose to run the script after setting up Telligent Analytics 3.7, you will need to re-process your web analytics data. To run this script, simply locate the migrate_web_analytics.sql script from the Telligent Analytics installation and run it on your Telligent Community or Telligent Enterprise database. It is strongly advised that you try this once on a non-production server using a backup of your database. Depending upon how much data you have in your cs_WebAnalytics table, this script could take some time to run. By running it first in a non-production environment, you will be able to gauge how much time will be needed for the production migration.

Will I lose any data?

Reporting data (metrics) will not be lost in the transfer from Telligent Analytics 3.6 to Telligent Analytics 3.7. Telligent Analytics copies data from your Telligent Community or Telligent Enterprise database to use for report generation in Analytics. Therefore, the data remains intact when upgrading to Telligent Analytics 3.7, but does require a reprocessing of all data.

There are a few areas that are not transferable to Telligent Analytics 3.7 and will require the user to reestablish them once Telligent Analytics 3.7 has been set up. These areas include:

Custom dashboards created by individual users
Subscriptions created by individual users
Roles/permissions
Tracked topics
Custom reports (please save custom reports and manually reestablish them in your 3.7 site)

Replacing the Extended Analytics module

Telligent Analytics 3.7 includes a new Extended Analytics module replacement. Installing this module is much easier to install in 3.7 than it was in 3.6. However, the 3.6 module must be removed before installing the new one.

To uninstall the old Extended Analytics module (if you didn't complete this step when installing Telligent Evolution):

Delete the CommunityServer.ExtendedAnalytics.dll file from the [Telligent Community or Telligent Enterprise site]\bin directory.
If your Telligent Community or Telligent Enterprise site is running in a web farm, make sure you do this on each web server.

Completing the upgrade

Follow all of the steps in the Full Installation guide, including the steps to install the new Extended Analytics and Analytics URLs.

Forum Post: RE: Custom dashboard + info con underlying DB structure

JanaCarter [Telligent] — Tue, 15 Nov 2011 17:03:00 GMT

Hi Andrea:

Apologies for the delay in response. For documentation on creating custom reports, including custom dashboards, you can go here (telligent.com/.../custom-reports.aspx). The part that will be the trickiest is the permissions. If you want to limit who can see the dashboard, you will first need to:

Create the new dashboard
Add reports to it
Then create a new role (Settings panel)
Add users to that role
Then ensure that new dashboard is only visible by that new role.

You can only restrict who sees a report, not who sees what data within a report (permissions is at the report level, not data level).

I hope this helps.

Jana Carter

Telligent Program Manager

Wiki Page: About Web Analytics 3.6 and 3.7

Jenny Jarrard — Thu, 20 Oct 2011 20:46:00 GMT

What is Web Analytics?

Web Analytics is the collection, analysis, and reporting of information about Internet traffic on your Web site. Telligent Analytics 3.x introduces all three stages of this process for use with your Telligent Evolution site.

How is data collected?

Telligent Evolution includes an additional assembly (ExtendedAnalytics.dll) that runs on your community site to collect traffic information. This assembly includes an HttpModule that subscribes to the End Request event of every page request, then records detailed information about each request made to the community site.

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: dynamicstyle.aspx)
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution / Telligent Enterprise brand and is not compatible with other Web sites.

How does this approach differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

Some drawbacks of these technologies:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers.
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community/context-specific information about the page requested (i.e., Which community group, section, and post(s) are associated with the page?)

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database to ensure that the processing time and storage space consumed are both minimized.

How is the data analyzed?

Requests are imported into the Analytics database through a series of tasks, which include but are not limited to: WebAnalyticsRawData and WebAnalyticsBulkProcessingTask. These unique tasks process and organize requests based on user and session information. Information about individual views, statistics on page requests, and browser and referrer information are also processed as part of these tasks.

Telligent Analytics makes use of page views to more accurately reflect true page views for actual user visits. The Web Analytics tasks differentiate between browser views, RSS views, and robot or crawler views; it then stores each of these types separately in the Analytics database for reporting. The primary means of differentiating between these types is through intelligent parsing of the Http User Agent string passed with the request.

Pre-calculated roll-up data is used for page views as well as topics and sentiment.

In the directory where you install the Telligent Analytics 3.x tasks, there is a configuration file named WebAnalytics.config. This holds the current list of regular expressions used to identify common user agent strings, broken out by category. It may be necessary to update this file periodically as new user agents are introduced. Check the Telligent Web site periodically for published updates to this file.

What reports are included?

Telligent Analytics 3.x includes a comprehensive set of reports built around views, visitors, pages, and referrers. Here is a list of the different sections of reports included with Telligent Analytics 3.x:

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

A note about Web Analytics if you are running a Telligent Evolution Mobile site

If you elected to install your Telligent Evolution Mobile site as a child site of the Telligent Evolution site (for example, mobile.mycommunity.com) and you are also running Web Analytics on your community, you will need to add a remove statement for Web Analytics to your mobile site's web.config file. Locate the following module and add the highlighted line:

  <system.webServer>     <modules runAllManagedModulesForAllRequests="true">       <remove name="Telligent.Evolution" />       <remove name="JavascriptAnalyticsHttpModule" />     </modules>

You need to make this change because the site is already inheriting the module from the community.

Wiki Page: How do I enable logging in my Task Service?

Jenny Jarrard — Thu, 13 Oct 2011 18:34:00 GMT

If you are using the Analytics Runner to execute your tasks in lieu of the Task Service, logging is enabled by default and no action is required. The HRSTracelog.log is located in your Tasks folder.

To enable error logging, open the Telligent.Tasks.Service.exe.config file located where your task service is installed, and un-comment the system.diagnostics section:

<system.diagnostics>     <trace autoflush="true">       <listeners>         <remove name="DefaultTraceListener" />         <add name="myListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="HRSTraceLog.log" />       </listeners>     </trace>   </system.diagnostics>

Then restart the task service. The next time any task runs, it will output a file in the same directory called HRSTraceLog.log.

This log file can grow very large, very quickly and so should only be enabled for brief periods of time as required for diagnosing problems with importing data.

Wiki Page: Configuring the Web Analytics task to write data to a separate database

Jenny Jarrard — Wed, 12 Oct 2011 21:17:00 GMT

This document explains how to configure the Web Analytics tasks to write data to a database other than the main community database.

Why would I need to store this data in a separate database?

If your site receives a lot of traffic, this data can take up a lot of disk space, requiring you to store this data in a separate database.

You may also wish to have these files in a separate database to schedule database backups on them separately from the community database backups. This data is only used for reporting purposes and is not as integral to the site as the other database files are.

The processing of this data (by the Web Analytics tasks) also adds some additional processing load to the database server. The more records the task has to process, the greater the load. You may wish to move this to a separate database server for performance reasons. Note that moving it to a separate database on the same server will probably not have any effect on performance, but moving it to a separate database server certainly will.

Walk-through

This walk-through assumes you have already successfully installed the Telligent Analytics site and Task Service, and that you have followed the install the Extended Analytics module instructions on your community site. These steps are updates that must be made to correctly configured files.

I. Create and configure the database

Create a new database in which to store these records. You can use any unique database name. For this walk-through, we assume the database is named CommunityWebAnalytics.

If you are using Telligent Analytics 3.6, run ExtendedAnalytics.sql on the new database to create the cs_WebAnalytics table and related stored procedures. This file can be found in the Telligent Analytics installer package in the ExtendedAnalytics folder.

If you are using Telligent Analytics 3.7, run EA_Separate_Database.sql on the new database to create the te_WebAnalytics table and related stored procedures. This file can be found in the Telligent Analytics installer package in the SQL folder.

II. Update the ExtendedAnalytics module configuration

We want to update the Extended Analytics module configuration to write to the new database. These changes will all be made to files in the Web root folder of your Evolution site.

Open the ExtendedAnalytics.config file, which is located at the root directory of your community site files.

Change the value for UseDefaultConnectionString to 0:

<UseDefaultConnectionString>0</UseDefaultConnectionString>

Add a new connection string entry in connectionStrings.config (located in the Web root folder of your Evolution site) that points to the CommunityWebAnalytics database.
```
<add name="WebAnalytics"
  connectionString="Server=(local);
  Trusted_Connection=True;
  Database="CommunityWebAnalytics;" />
```
Ensure the value for CustomConnectionStringName matches the name of the connection string you just created in connectionStrings.config.
```
<CustomConnectionStringName>WebAnalytics</CustomConnectionStringName>
```
If you are running Telligent Community or Telligent Enterprise in a virtual directory off the root of your domain, you will need to perform the following steps:
1. In the ExtendedAnalytics.config file in the Telligent Evolution Web site, find the following section
```

```
2. Uncomment this and change the /testweb/ portion of the URL so that it corresponds with the URL where you've installed Telligent Community; for example, if your community is called http://foo.com/community/, the value should read /community/analytics.ashx.
Read more about the module configuration options.

III. Update the Web Analytics tasks in the task configuration

Next, we want to update the Web Analytics tasks to pull data from the CommunityWebAnalytics database. These changes will all be executed in task files located where your Telligent Analytics Task Service is installed.

Add a new connection string to connectionStrings.config that looks like this:
```
<Add name="Community1WebAnalytics"
  connectionString="Server=(local);
  Database=CommunityWebAnalytics;
  Trusted_Connection=True;" />
```
Be sure to specify a valid connection string to your CommunityWebAnalytics database.

Add a site to the TaskStrings.config file to use the new WebAnalytics connection string.

<!-- DECLARE SITES -->
<Sites>
  <Site name = "Community1"
    Community = "Community1"
    Membership = "Community1SharedMembership"
    Reporting = "Community1Reporting"
    WebAnalytics="Community1WebAnalytics"
    siteSchema = "community" />
</Sites>

Update the Web Analytics tasks entries in TaskStrings.configto use this connection string alias as its source database.
Find the <Task> entry for the following Web Analytics tasks: WebAnalyticsUserAgentTask and WebAnalyticsRawData. Update the Source attribute to use the WebAnalytics site you just added in the previous step. (Replace Community with WebAnalytics.)
```
<Task name="WebAnalyticsRawData"
  DestinationTable="IF_WebAnalytics"
  ImportIdField=""
  RequiredTasks=""
  Source="WebAnalytics"
  Destination="Reporting"
  LastProcessedDateQuery="...">
```
Save these files, then restart the Telligent Analytics Task Service in the services list.

Wiki Page: Setting up shared membership

Alex Crome — Wed, 12 Oct 2011 20:46:00 GMT

Important: To use the Shared Membership configuration, you must first create a site in Settings using the default Forms authentication mode. Users in Analytics are tied to Report Sites, and a Site must first exist before any logins can be created. Make sure you have created a Report Site before enabling Shared Membership.

Note: Due to a fundamental change that occurred in the Roles system in Telligent Community 5.0 / Enterprise 2.0, the Shared Membership feature of Telligent Analytics does not directly integrate with existing community roles.

User logins can be shared with an existing community site, and Telligent Analytics roles can be created for these logins if desired. To use ASPNET membership roles instead of specifying allowed users (instructions below), you need to download an ASPNET membership tool and use it to create and assign these roles to users.

Procedure

Locate the Web.config and Web.SharedMembership.config files in your Web directory.
Rename the Web.config file. Telligent recommends renaming it something like Web.default.config.
Rename the Web.SharedMembership.config file to Web.config.
Locate the connectionStrings.config file, also in the Web directory.
Update the following connection string:
1. aspnet_membership
  
  A string that points to the database where your membership tables are located. This is usually pointed at your Telligent Evolution community.
  
  <add name="aspnet_membership" connectionString="server=(local);database=TelligentCommunity;Trusted_Connection=True;" />
Open the Web.config file (the one you renamed in Step 3 above). Do the following:
1. locate the <membership defaultProvider> section. This can be located by searching the Web.config file for "<membership" (no closing bracket).
  
  Under <add name="aspnet_membership_provider"...> look for applicationName="telligent_community" and ensure that applicationName matches the application name of your Telligent Evolution Platform community (found in the table of your membership database in the database table aspnet_applications).
2. If you are using Telligent Analytics 3.7, you must perform this step. Locate the <roleManager> section. This can be located by searching the web.config file for "<roleManager" (no closing bracket). Ensure there is a valid provider added, for example:
```
<roleManager defaultProvider="SqlProvider"      enabled="true"      cacheRolesInCookie="false"        >       <providers>         <add           name="SqlProvider"           type="System.Web.Security.SqlRoleProvider"           connectionStringName="aspnet_membership"           applicationName="your-application-name-from-previous-step" />       </providers>     </roleManager>
```
3. Locate the <authorization> section.
  
  Add additional users by adding lines similar to this one:
  
  <allow users="admin" />
  
  Note: If you instead wish to allow any users with a valid login to have access to the Analytics site, replace the <deny users="*" /> line with <deny users="?" />. This way you don't have to specify all the users individually.
4. Save the Web.config file.
Navigate to the /admin/ folder and open the Web.config file found in this directory. Add users that you wish to grant access to the Control Panel in Analytics.
1. Add additional users by adding lines similar to this one:
  
  <allow users="admin" />
2. Save the Web.config file.
If you are using Telligent Analytics 3.7, you must perform this step. Ensure that the database user for the aspnet_membership connection string has the following three roles to the Evolution database:
- aspnet_Roles_BasicAccess
- aspnet_Roles_FullAccess
- aspnet_Roles_ReportingAccess

Wiki Page: Important concepts and features

Jenny Jarrard — Tue, 04 Oct 2011 20:35:00 GMT

Telligent Analytics comprises a set of strong data collection and interpretation tools which collectively provide you with wide-scoped, accurate insight into your community's data, influencers, and sentiment.

This section of the User's Guide describes each of the component concepts of the application and then links the concepts to the queries or reports providing the data.

This section contains the following articles:

About Web Analytics - for 3.5, see this document; for 3.6 and 3.7, see this document.
Answer rate, reply rate, and time-to-solution explained
Buzz
1. Default data sources for external buzz
2. Why do I need to enter a Flickr API key and a Live AppID key in my task service config file?
Scoping
Search
Users
Volatile topics

Forum Post: Re: Download location for telligent Analytics 3.6

JanaCarter [Telligent] — Fri, 16 Sep 2011 06:25:00 GMT

Please contact Support for product download information.

Thank you

Jana

On Sep 15, 2011, at 11:14 PM, "Faster fene" <bounce-Faster_fene@communities.telligent.com> wrote:

Hi ,

I need analytics product to install on my machine.

Anybody knows how can I get these files ?

thanks

Wiki Page: Reports

Jenny Jarrard — Thu, 08 Sep 2011 20:12:00 GMT

Telligent Analytics includes in-depth views into your community in five key areas:

Buzz
1. Summary
  - Buzz key vital signs
2. My site buzz
  - Top topics
  - People
  - Tracked topics
  - Volatile topics
  - Top searches
  - Popular tags
3. Listening externally
  - Twitter buzz
  - Top topics
  - People
  - Sources
4. Buzz by user type
  - Asker buzz
  - Answerer buzz
  - Influencer buzz
  - Originator buzz
  - New users buzz
5. Buzz sentiment
  - Overall sentiment
  - Sentiment per topic
  - Sentiment for power users
Collaboration
1. Summary
  - Collaboration key vital signs
2. Groups
  - Summary
  - Activity
  - New groups
3. Forums
  - Summary
  - Views
  - Discussion threads
  - Q/A threads
  - Answer rates
  - Reply rates
  - Popular content
4. Blogs
  - Summary
  - Views
  - Posts
  - Comments
  - Popular content
5. Wikis
  - Summary
  - Views
  - Contributions
  - Pages
  - Revisions
  - Comments
  - Popular content
6. Media galleries
  - Summary
  - Views
  - Files
  - File size
  - Comments
  - Popular content
Support
1. Summary
  - Support key vital signs
2. Forum users
  - Contributors
  - Moderators
  - Top answerers
  - Top askers
3. Thread life cycle
  - Answer rate
  - Reply rate
  - Threads
  - Time-to-solution
Users
1. Summary
  - User key vital signs
2. User behavior
  - Active users
  - Find a user
  - Sign ins
3. User types
  - Summary
  - Answerer
  - Asker
  - Commenter
  - Connector
  - Influencer
  - Originator
  - Moderator
4. User demographics
  - User demographics
  - Users in roles
  - Total users
5. Sentiment
  - Users sentiment
Web Analytics
1. Summary
  - Web Analytics key vital signs
2. Views
  - Page views
  - RSS page views
  - Most-viewed pages
3. Visitors
  - Total visitors
  - Time on site
  - Depth of visit
4. Loyalty
  - Visitor frequency
  - Visitor recency
  - Exit ratio
5. Usage
  - Browser usage
  - Search keywords
  - Traffic sources
6. Exceptions
  - Exceptions

Related information

Favorite forum reports

(Please visit the site to view this video)

Identify inactive groups

(Please visit the site to view this video)

Wiki Page: Email subscriptions to reports

Jenny Jarrard — Thu, 08 Sep 2011 19:51:00 GMT

You can subscribe to reports via email if you are using one of the membership configurations (shared membership or Windows authentication). Once shared membership or Windows authentication mode is successfully configured, the Subscribe option displays in the Options menu of a report.

To subscribe to emails for a particular report:

Click Options on the report to which you want to subscribe, then click Subscribe. You should see the Subscriptions count in the top right increment by one.

Click this link to view your active subscriptions. This page gives you the options to remove a subscription or to edit the delivery options for a subscription. Clicking the red X icon will permanently remove the subscription. Clicking the gray wrench icon will expand the subscription options for this subscription.

You can set the email delivery frequency in days, weeks or months. The default email delivery frequency for reports is once per day. An email is sent to you the first time the EmailTask runs each day. (This task is set to run every two hours by default.)

Days

You can modify the delivery frequency by increasing the days from one to 10 days.

Weeks

You can also schedule a Weekly delivery by changing Day(s) to Week(s). Select the check boxes for the specific day(s) of the week on which you wish to receive emails.

Months

Changing Days(s) to Month(s) will present additional options for monthly delivery.

You can even subscribe to the same report multiple times, and schedule several precise monthly deliveries. For example, you could subscribe to a specific report twice, having one subscription delivered on the first day of each month and the second subscription delivered on the 15th day of the month.

Telligent Analytics

Wiki: Telligent Analytics Product Documentation

Wiki Page: Tasks

Wiki Page: About Web Analytics (3.5)

What is Web Analytics?

How is data collected?

How does this approach differ from other Web Analytics solutions?

How is the data stored?

How is the data analyzed?

What reports are included?

Wiki Page: 1. Full installation for release 3.7

In this Article

System requirements

Web server requirements

Development framework requirements

Tasks service requirements

Database requirements

Set up the Web server

Set up the database

Connect Web site to the database

Configure Telligent Analytics Web settings

Set up Web Analytics (Extended Analytics)

Install Anaytics Task Runner

Install Tasks Service

Forum Post: RE: Telligent 3.6 bin directory

Forum Post: RE: Object Reference not set to an object when clicking Web Analytics

Forum Post: RE: Anonymous Visitors for Private Groups

Forum Post: RE: limit analytics child app to the community adminsitrators group

Forum Post: RE: Errors while trying to set up first time.

Wiki Page: 1. Full installation through release 3.6

In this Article

System requirements

Web server requirements

Development framework requirements

Tasks service requirements

Database requirements

Set up the Web server

Set up the database

Connect Web site to the database

Configure Telligent Analytics Web Settings

Set up Web Analytics (Extended Analytics)

Upgrade

Install

Install Tasks Service

Wiki Page: 3.7 upgrade FAQ

Which versions of Telligent Evolution are compatible with Telligent Analytics 3.7?

How do I upgrade from an older version of Telligent Analytics to Telligent Analytics 3.7?

Why a new install?

Upgrade web analytics data

Will I lose any data?

Replacing the Extended Analytics module

Completing the upgrade

Forum Post: RE: Custom dashboard + info con underlying DB structure

Wiki Page: About Web Analytics 3.6 and 3.7

In this Article

What is Web Analytics?

How is data collected?

How does this approach differ from other Web Analytics solutions?

How is the data stored?

How is the data analyzed?

What reports are included?

A note about Web Analytics if you are running a Telligent Evolution Mobile site

Wiki Page: How do I enable logging in my Task Service?

Wiki Page: Configuring the Web Analytics task to write data to a separate database

Why would I need to store this data in a separate database?

Walk-through

I. Create and configure the database

II. Update the ExtendedAnalytics module configuration

III. Update the Web Analytics tasks in the task configuration

Wiki Page: Setting up shared membership

Procedure

Wiki Page: Important concepts and features

Forum Post: Re: Download location for telligent Analytics 3.6

Wiki Page: Reports

Related information

Favorite forum reports

Identify inactive groups

Wiki Page: Email subscriptions to reports

Days

Weeks