Telligent Analytics Product Documentation

Telligent Analytics 3.7 hotfix notes

Jenny Jarrard — Fri, 25 May 2012 16:09:12 GMT

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 5/25/2012 11:09:12 AM

The following list details bugs that were fixed or will be fixed in chronological hotfixes. The hotfixes are cumulative, meaning that the more recent hotfix will contain fixes incorporated in previous hotfixes. Please contact Telligent Support to request a hotfix, ask questions about specific bug fixes or get additional help in applying a hotfix to your environment.

16 May 2012: 3.7.342.24831

19317 - Wiki edits are now captured correctly from the community so that it can be reported on appropriately (error previously showed cs_Sections as not found).
19286 - You can now successfully subscribe to an RSS feed for the Buzz Key Vital Signs Topic Tracker report.
18958 - Long-running tasks no longer cause deadlocks due to Evolution processes needing table or row lock on the ForumPostData task.
18564 - The help text was updated to reflect the 1, 3 and 7 day views for average time-to-solution for the "Answer Rate for Groups & Forums" and "Reply Rate for Groups & Forums" reports. Previously it showed a 2-day view in the help text that did not match the actual report.
18455 - All RSS feeds and CSV exports work correctly.
18450 - The Blogs > BlogsOverview report now works without timing out.
18031 - When using offload appliance for SSL, you can now successfully scope reports by specific groups without seeing errors.
17365 - The Users > Active Users > Contributions For Owner report now shows all the contributions made by the administrator or owner, including blog comments.
16747 - The Collaboration > Blogs > Summary report now correctly shows the comment count for any blog post that has been edited.

15 March 2012: 3.7.342.23287

16427 - All reports correctly show users, regardless of when they registered for the community. Previously, some reports, including Top Askers, did not correctly show the username of the user.

22 February 2012: 3.7.342.22967

14507 - Update processes to import community content will now perform well, even if the process to import updated user data runs at the same time. Previously this was causing deadlocks for communities with large amounts of community content and more than one community being reported on.
14554 - Telligent Analytics now performs well when processing a large volume of web analytics data, both current and historical, including pages viewed, session duration, start date, end date, and more.
14793 - The Collaboration > Blogs > Popular Content > Most Viewed Blogs report now shows the correct number of blog views for each blog and the sort order is now correctly by most viewed first down to least viewed.
14795 - We now correctly determine when a forum thread is the originating question or discussion (top level post) when pulling summary data for forums.
15415 - For communities with a large volume of forum posts, the speed of the report calculation for the average time to reply is now optimized.
15491 - The web analytics reports now accurately reflect the full day's worth of page views, RSS views, browser usage, page exits, visitors, sessions, profile views, referrers, and user agents.
15725 - As you apply database schema updates from version to version, you will no longer see errors about conflicting variable names.
15911 - We now incrementally import user display name data from the community rather than trying to load it all at once, which can cause blocking within the community database.

17 January 2012: 3.7.342.21980

14245 - There is no longer a message in Exceptions.txt error that "te_vw_Sections" is an invalid object name when you run the SectionData_Updates and WikiData_Updates tasks using Analytics Runner. This error previously occurred because a query was executed against the Telligent Analytics database but had reference to tables inside the Telligent Evolution database.
13489 - The PctNewVisitorsTimeSliceData task no longer causes an arithmetic overflow error when adding a large numbers of users. Previously a large number of users (above 22 million) could cause the task to exceed its maximum limit. This was corrected with a code change in the task.
14243 - There is no longer a message in Exceptions.txt error that there is "Incorrect syntax near ',' when you run the UserData_Updates task using Analytics Runner. This error previously occurred if there were no failed password attempts due to a line of SQL code appearing incorrectly in that case.
14645 - There is no longer an issue with the UserDisplayNameData task returning an incorrect number of new Telligent Evolution users in the csr_UserData table when the number of new Evolution users tops 1,000. This was occurring due to a limitation in the selection query.

28 November 2011: 3.7.342.20774

11529 - There is no longer a BulkCopy SQL exception that states in the log file, "The given value of type String from the data source cannot be converted to type nvarchar of the specified target column," after attempting to run the following tasks to completion with the Analytics Runner:
- 1DayAnswerRateTimeSliceData
- 1DayReplyRateTimeSliceData
- 3DayAnswerRateTimeSliceData
- 3DayReplyRateTimeSliceData
- 7DayAnswerRateTimeSliceData
- 7DayReplyRateTimeSliceData
- AnonymousVisitorsTimeSliceData
- AnswerersTimeSliceData
- AskersTimeSliceData
- AvgConnectionsPerUserTimeSliceData
- AvgPagesViewedTimeSliceData
- AvgTimeOnSiteTimeSliceData
- AvgTimeToReplyTimeSliceData
- AvgTimeToSolutionTimeSliceData
- CommentersTimeSliceData
- ConnectorsTimeSliceData
- ExternalSearchesTimeSliceData
- FirstTimeVisitorsPerDayTimeSliceData
- FirstTimeVisitorsTimeSliceData
- Harvest.Tasks.UserContributionMetricsTask
- InfluencersTimeSliceData
- InternalSearchesTimeSliceData
- ModeratorsTimeSliceData
- NatLangTopicMentionRollup
- NatLangUserMentionRollup
- OriginatorsTimeSliceData
- OverallAnswerRateTimeSliceData
- OverallReplyRateTimeSliceData
- PctContributionsByExitingUsersTimeSliceData
- PctNewVisitorsTimeSliceData
- RegisteredVisitorsTimeSliceData
- ReturneeRateTimeSliceData
- ReturningVisitorsPerDayTimeSliceData
- ReturningVisitorsTimeSliceData
- SingletonsTimeSliceData
- TopReferrerTimeSliceData
- TotalPagesViewedTimeSliceData
- TotalPageViewsTimeSliceData
- TotalRssViewsRemoteOnlyTimeSliceData
- TotalSessionsTimeSliceData
- TotalViewsRemoteOnlyTimeSliceData
- TotalVisitorsPerDayTimeSliceData
- TotalVisitorsTimeSliceData
- TrafficSourcesRollup
- UserConnectionMetricsRawDataTask
- UserDisplayNameData_Updates
- VisitorRecencyRollupTask
Previously, usernames over 64 characters could trigger an issue with unmatching source and destination data fields that prevented the tasks from completing. We increased the destination field width to match the source field width to correct the problem.

15 November 2011: 3.7.342.20509

11391 - The Most Active Blogs and Total Views Per Blog reports no longer show an inconsistent number of time period views for the same blog. This inconsistency was caused by reports being filtered by different IDs. The BlogViewsDetailedReport.cs query now aggregates blog views by the section ID instead of the PostID.
11329 - We now ensure a user's own reply to a forum thread is not counted in the Avg Time to Reply reports. Previously, a thread owner replying to his/her own thread with a bump could skew the "How fast my community's threads are getting replies" metric. This was fixed with a change to TaskStrings.config.
11293 - Double-byte characters in Telligent Evolution, such as used by Chinese or other non-English languages, no longer display improperly after being imported into Telligent Analytics. Previously when the content was first created and inserted into Telligent Analytics, it retained the correct formatting, but once updated the characters changed into question marks. The SQL was updated to use N'value' instead of 'value'.
11328 - The ForumReplyRatesDetailedReport and ReplyRatesPerDayData reports now properly report the number of forum replies. Previously they might have excluded some replies or not filtered a thread starter's own replies when calculating.

24 October 2011: 3.7.342.20106

1 - Fixed an issue with ExtendedAnalytics that required modifying the ExtendedAnalytics.config file with an out of box install of a community site using a virtual directory.
6 - Added a script to create the EA table and sproc and correct file spelling.
9 - TotalMediaViewsPerGalleryReport now displaying "N/A" for most viewed file if there are no files in the gallery.
10 - External link was not working; decision was made to remove the external URL from this report. Note: It's available via the click-through.
13 - Fixed issue in RSS for a number of reports. For four of the reports, a fix to ReportBase (Line 994): (ContributionsPerUserReport, TotalRolesReport, TotalViewsPerWikiPageReport, UsersPerDomainDetailedReport). For the other report (ExceptionsDetailedReport), a SanitizeXML function was needed.
14 - Fixed an issue in UserTypesOneColumnByGroupReport - The CSV handler caused a yellow screen due to a missing Trend column. I added the Trend column to the query to ensure that it matched the visible report.
15 - Reverted the X-FRAME-OPTIONS change in order to get embedded reports working again.
16 - Added a coalesce and left join to make sure and include all views.
18 - Fixed an issue with ContributionsByUserByDateReport where the post title for blog comments was not showing up.
19 - Fixed an issue with ReplyRatesPerDayData task ignoring replies made to the first threads created in Evolution.
20 - Using HttpContext username to get a user instead of relying on reportParams.UserId.
22 - Changed Increment Update tasks to honor dates (previously they had pushed dates back 24hrs). See 3.6 Hotfix change 19037.
24 - Updated ForumPostData_Updates task to use checksum instead of 'top 1000' method, removed importId use as well.
25 - Fixed an issue where ForumThreadData_Updates task was not sorting the data it pulled and therefore would not eventually update all records. Also fixed performance issues with the task by removing the top 1000 limit; it now only updates records that need to be updated.
26 - Updated BlogCommentData_Updates merge task to remove 'top 1000' and add checksum method.
27 - BlogPostData Updates - Moved top 1000/checksum techniques from 3.6 to 3.7.
28 - Changed WikiData_Updates to IncrementalUpdateMergeQueryTask, and updated its query to remove top 1000 and to add a mergequery using checksum method 29 - WikiCommentData_Updates checksum/top 1000 fix.
30 - WikiRevisionData. Also fixed an issue in #6 where ImportDate was not honored.
33 - ImportDt = ImportDt minus 1 day 34 - UserFriendShipData Updates - As this task is nota merge task, the updates copy all the data over and then just update. It's simpler and faster to make the task non-incremental as this would bring all of the data over via BCP and skip the unneeded update step.
35 - Fixed an issue where GroupData_Updates task was not sorting the data it pulled and therefore would not eventually update all records. Also fixed performance issues with the task by removing the top1000 limit; it now only updates records that need to be updated.
35 - Fixed an issue where MediaCommentData_Updates task was not sorting the data it pulled and therefore would not eventually update all records. Also fixed performance issues with the task by removing the top 1000 limit; it now only updates records that need to be updated.
37 - Removed UserDisplayNameData_Updates task and changed UserDisplayNameData task to NonIncrementalQueryTask, the same change that was made in 3.6 hotfix.
38 - UserData Updates - Removed top 1000, removed < @ImportID and ensured that its using the same 3.6 Checksum technique.
40 - MediaPostData updates - Ported updates to MergeQuery section from 3.6 and removed top 1000 and @ImportID checks from the add'l queries.
42 - Removed 'top 1000' and added checksum comparison to the merge query for WikiPageData_Updates (same as in 3.6 hotfix).
43 - ReplyRatesPerDayData task RollupGroupId <> NULL for threads with no replies.
44 - Number 11 under Security Options starts with "specify" instead of "Specify" .
45 - Fixed an issue where UserFriendshipData task was not properly set up to run as a NonIncrementalTask. Needed to remove the top 1000 limit and the ImportIdField.
46 - Removed that Updates.sql and added a schema patch instead to remove the tasks.
47 - Corrected ReplyRatesPerDayData query where numerator and denominator values were switched.
49 - ReadMe spelling errors.
51 - Added logic to exclude Post and Wiki Drafts.
52 - RSSViewsReport are all zero, even though RSSs have been viewed.
54 - TheActiveUsersData task would not execute until all of its required tasks had executed at least once.
55 - Media Gallery RSS hit was not logged in te_WebAnalytics.

Telligent Analytics 3.7 hotfix notes

Jenny Jarrard — Fri, 25 May 2012 15:33:01 GMT

Revision 2 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 5/25/2012 10:33:01 AM

16 May 2012: 3.7.342.24831

19317 - Wiki edits are now captured correctly from the community so that it can be reported on appropriately (error previously showed cs_Sections as not found).
19286 - You can now successfully subscribe to an RSS feed for the Buzz Key Vital Signs Topic Tracker report.
18958 - Long-running tasks no longer cause deadlocks due to Evolution processes needing table or row lock on the ForumPostData task.
18564 - The help text was updated to reflect the 1, 3 and 7 day views for average time-to-solution for the "Answer Rate for Groups & Forums" and "Reply Rate for Groups & Forums" reports. Previously it showed a 2-day view in the help text that did not match the actual report.
18455 - All RSS feeds and CSV exports work correctly.
18450 - The Blogs > BlogsOverview report now works without timing out.
18031 - When using offload appliance for SSL, you can now successfully scope reports by specific groups without seeing errors.
17365 - The Users > Active Users > Contributions For Owner report now shows all the contributions made by the administrator or owner, including blog comments.
16747 - The Collaboration > Blogs > Summary report now correctly shows the comment count for any blog post that has been edited.

15 March 2012: 3.7.342.23287

16427 - All reports correctly show users, regardless of when they registered for the community. Previously, some reports, including Top Askers, did not correctly show the username of the user.

22 February 2012: 3.7.342.22967

14507 - Update processes to import community content will now perform well, even if the process to import updated user data runs at the same time. Previously this was causing deadlocks for communities with large amounts of community content and more than one community being reported on.
14554 - Telligent Analytics now performs well when processing a large volume of web analytics data, both current and historical, including pages viewed, session duration, start date, end date, and more.
14793 - The Collaboration > Blogs > Popular Content > Most Viewed Blogs report now shows the correct number of blog views for each blog and the sort order is now correctly by most viewed first down to least viewed.
14795 - We now correctly determine when a forum thread is the originating question or discussion (top level post) when pulling summary data for forums.
15415 - For communities with a large volume of forum posts, the speed of the report calculation for the average time to reply is now optimized.
15491 - The web analytics reports now accurately reflect the full day's worth of page views, RSS views, browser usage, page exits, visitors, sessions, profile views, referrers, and user agents.
15725 - As you apply database schema updates from version to version, you will no longer see errors about conflicting variable names.
15911 - We now incrementally import user display name data from the community rather than trying to load it all at once, which can cause blocking within the community database.

17 January 2012: 3.7.342.21980

14245 - There is no longer a message in Exceptions.txt error that "te_vw_Sections" is an invalid object name when you run the SectionData_Updates and WikiData_Updates tasks using Analytics Runner. This error previously occurred because a query was executed against the Telligent Analytics database but had reference to tables inside the Telligent Evolution database.
13489 - The PctNewVisitorsTimeSliceData task no longer causes an arithmetic overflow error when adding a large numbers of users. Previously a large number of users (above 22 million) could cause the task to exceed its maximum limit. This was corrected with a code change in the task.
14243 - There is no longer a message in Exceptions.txt error that there is "Incorrect syntax near ',' when you run the UserData_Updates task using Analytics Runner. This error previously occurred if there were no failed password attempts due to a line of SQL code appearing incorrectly in that case.
14645 - There is no longer an issue with the UserDisplayNameData task returning an incorrect number of new Telligent Evolution users in the csr_UserDAta table when the number of new Evolution users tops 1,000. This was occurring due to a limitation in the selection query.

28 November 2011: 3.7.342.20774

11529 - There is no longer a BulkCopy SQL exception that states in the log file, "The given value of type String from the data source cannot be converted to type nvarchar of the specified target column," after attempting to run the following tasks to completion with the Analytics Runner:
- 1DayAnswerRateTimeSliceData
- 1DayReplyRateTimeSliceData
- 3DayAnswerRateTimeSliceData
- 3DayReplyRateTimeSliceData
- 7DayAnswerRateTimeSliceData
- 7DayReplyRateTimeSliceData
- AnonymousVisitorsTimeSliceData
- AnswerersTimeSliceData
- AskersTimeSliceData
- AvgConnectionsPerUserTimeSliceData
- AvgPagesViewedTimeSliceData
- AvgTimeOnSiteTimeSliceData
- AvgTimeToReplyTimeSliceData
- AvgTimeToSolutionTimeSliceData
- CommentersTimeSliceData
- ConnectorsTimeSliceData
- ExternalSearchesTimeSliceData
- FirstTimeVisitorsPerDayTimeSliceData
- FirstTimeVisitorsTimeSliceData
- Harvest.Tasks.UserContributionMetricsTask
- InfluencersTimeSliceData
- InternalSearchesTimeSliceData
- ModeratorsTimeSliceData
- NatLangTopicMentionRollup
- NatLangUserMentionRollup
- OriginatorsTimeSliceData
- OverallAnswerRateTimeSliceData
- OverallReplyRateTimeSliceData
- PctContributionsByExitingUsersTimeSliceData
- PctNewVisitorsTimeSliceData
- RegisteredVisitorsTimeSliceData
- ReturneeRateTimeSliceData
- ReturningVisitorsPerDayTimeSliceData
- ReturningVisitorsTimeSliceData
- SingletonsTimeSliceData
- TopReferrerTimeSliceData
- TotalPagesViewedTimeSliceData
- TotalPageViewsTimeSliceData
- TotalRssViewsRemoteOnlyTimeSliceData
- TotalSessionsTimeSliceData
- TotalViewsRemoteOnlyTimeSliceData
- TotalVisitorsPerDayTimeSliceData
- TotalVisitorsTimeSliceData
- TrafficSourcesRollup
- UserConnectionMetricsRawDataTask
- UserDisplayNameData_Updates
- VisitorRecencyRollupTask
Previously, usernames over 64 characters could trigger an issue with unmatching source and destination data fields that prevented the tasks from completing. We increased the destination field width to match the source field width to correct the problem.

15 November 2011: 3.7.342.20509

11391 - The Most Active Blogs and Total Views Per Blog reports no longer show an inconsistent number of time period views for the same blog. This inconsistency was caused by reports being filtered by different IDs. The BlogViewsDetailedReport.cs query now aggregates blog views by the section ID instead of the PostID.
11329 - We now ensure a user's own reply to a forum thread is not counted in the Avg Time to Reply reports. Previously, a thread owner replying to his/her own thread with a bump could skew the "How fast my community's threads are getting replies" metric. This was fixed with a change to TaskStrings.config.
11293 - Double-byte characters in Telligent Evolution, such as used by Chinese or other non-English languages, no longer display improperly after being imported into Telligent Analytics. Previously when the content was first created and inserted into Telligent Analytics, it retained the correct formatting, but once updated the characters changed into question marks. The SQL was updated to use N'value' instead of 'value'.
11328 - The ForumReplyRatesDetailedReport and ReplyRatesPerDayData reports now properly report the number of forum replies. Previously they might have excluded some replies or not filtered a thread starter's own replies when calculating.

24 October 2011: 3.7.342.20106

1 - Fixed an issue with ExtendedAnalytics that required modifying the ExtendedAnalytics.config file with an out of box install of a community site using a virtual directory.
6 - Added a script to create the EA table and sproc and correct file spelling.
9 - TotalMediaViewsPerGalleryReport now displaying "N/A" for most viewed file if there are no files in the gallery.
10 - External link was not working; decision was made to remove the external URL from this report. Note: It's available via the click-through.
13 - Fixed issue in RSS for a number of reports. For four of the reports, a fix to ReportBase (Line 994): (ContributionsPerUserReport, TotalRolesReport, TotalViewsPerWikiPageReport, UsersPerDomainDetailedReport). For the other report (ExceptionsDetailedReport), a SanitizeXML function was needed.
14 - Fixed an issue in UserTypesOneColumnByGroupReport - The CSV handler caused a yellow screen due to a missing Trend column. I added the Trend column to the query to ensure that it matched the visible report.
15 - Reverted the X-FRAME-OPTIONS change in order to get embedded reports working again.
16 - Added a coalesce and left join to make sure and include all views.
18 - Fixed an issue with ContributionsByUserByDateReport where the post title for blog comments was not showing up.
19 - Fixed an issue with ReplyRatesPerDayData task ignoring replies made to the first threads created in Evolution.
20 - Using HttpContext username to get a user instead of relying on reportParams.UserId.
22 - Changed Increment Update tasks to honor dates (previously they had pushed dates back 24hrs). See 3.6 Hotfix change 19037.
24 - Updated ForumPostData_Updates task to use checksum instead of 'top 1000' method, removed importId use as well.
25 - Fixed an issue where ForumThreadData_Updates task was not sorting the data it pulled and therefore would not eventually update all records. Also fixed performance issues with the task by removing the top 1000 limit; it now only updates records that need to be updated.
26 - Updated BlogCommentData_Updates merge task to remove 'top 1000' and add checksum method.
27 - BlogPostData Updates - Moved top 1000/checksum techniques from 3.6 to 3.7.
28 - Changed WikiData_Updates to IncrementalUpdateMergeQueryTask, and updated its query to remove top 1000 and to add a mergequery using checksum method 29 - WikiCommentData_Updates checksum/top 1000 fix.
30 - WikiRevisionData. Also fixed an issue in #6 where ImportDate was not honored.
33 - ImportDt = ImportDt minus 1 day 34 - UserFriendShipData Updates - As this task is nota merge task, the updates copy all the data over and then just update. It's simpler and faster to make the task non-incremental as this would bring all of the data over via BCP and skip the unneeded update step.
35 - Fixed an issue where GroupData_Updates task was not sorting the data it pulled and therefore would not eventually update all records. Also fixed performance issues with the task by removing the top1000 limit; it now only updates records that need to be updated.
35 - Fixed an issue where MediaCommentData_Updates task was not sorting the data it pulled and therefore would not eventually update all records. Also fixed performance issues with the task by removing the top 1000 limit; it now only updates records that need to be updated.
37 - Removed UserDisplayNameData_Updates task and changed UserDisplayNameData task to NonIncrementalQueryTask, the same change that was made in 3.6 hotfix.
38 - UserData Updates - Removed top 1000, removed < @ImportID and ensured that its using the same 3.6 Checksum technique.
40 - MediaPostData updates - Ported updates to MergeQuery section from 3.6 and removed top 1000 and @ImportID checks from the add'l queries.
42 - Removed 'top 1000' and added checksum comparison to the merge query for WikiPageData_Updates (same as in 3.6 hotfix).
43 - ReplyRatesPerDayData task RollupGroupId <> NULL for threads with no replies.
44 - Number 11 under Security Options starts with "specify" instead of "Specify" .
45 - Fixed an issue where UserFriendshipData task was not properly set up to run as a NonIncrementalTask. Needed to remove the top 1000 limit and the ImportIdField.
46 - Removed that Updates.sql and added a schema patch instead to remove the tasks.
47 - Corrected ReplyRatesPerDayData query where numerator and denominator values were switched.
49 - ReadMe spelling errors.
51 - Added logic to exclude Post and Wiki Drafts.
52 - RSSViewsReport are all zero, even though RSSs have been viewed.
54 - TheActiveUsersData task would not execute until all of its required tasks had executed at least once.
55 - Media Gallery RSS hit was not logged in te_WebAnalytics.

Embedding a report in an external Web page

Jenny Jarrard — Thu, 03 May 2012 16:38:53 GMT

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 5/3/2012 11:38:53 AM

For release 3.5, 3.6, and 3.7: You can take full advantage of your reports by embedding them into any existing Web site. The embedded reports have the same look and feel as reports within Telligent Analytics and also have the same interactive capabilities for zooming into parts, turning lines on or off, and drilling down on a node.

Telligent Analytics allows you to embed Analytics reports in other external Web sites. Data shown on the embedded report will be the same as results you would see on the actual site. (The embedded report data will update as tasks run to import data into Analytics.)

This is accomplished by copying the embed code from a report's Options menu and pasting it in the HTML code of the external Web site.

To embed a report in an external Web site:

Click Options on the report you wish to embed, then click the Embed link.

The Options menu will expand, and you will see a box appear underneath the Embed link.
Click inside the box containing the embed code and copy the contents (right-click > Copy, or Ctrl+c).
Paste the contents inside the HTML body of the Web site in which you wish to embed this report. Here is a simple example:

<html><body>
<script type="text/javascript" src="..."></script>
</body></html>
Save the page to which you are adding the script. Now, when you load this page, you should see the embedded report.

Permissions

Embedded reports must request data from the Telligent Analytics Web site. If your Analytics site is locked down to deny anonymous access, users trying to view an embedded report will be prompted to supply credentials to view the report. This will happen each time a new session is initiated for a given user. If a user is unable to supply credentials, the embedded report will not display.

This permissions issue only applies if the Telligent Analytics site is on a separate server/domain from the site in which you are embedding the report. For example, if the Analytics site is set up as a virtual directory on top of a Telligent Enterprise site and the two sites share an authentication protocol, the request will already be authenticated for both sites - so a viewer will not have to supply credentials again.

Telligent Analytics 3.7 hotfix notes

Jenny Jarrard — Thu, 19 Apr 2012 18:35:56 GMT

Revision 1 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 4/19/2012 1:35:56 PM

15 November 2011: 3.7.342.20509

11391 - Blog views were inconsistent across reports.
11329 - We now ensure a person's own reply to a forum thread is not counted in the Avg Time to Reply reports.This was a bug fixed in 3.6, but now fixed in 3.7 as well.
11293 - Double-byte characters were not displaying properly due to Update tasks setting columns using Column='Value' instead of Column=N'Value. This was a bug fixed in 3.6, but now fixed in 3.7 as well.
11328 - ReplyRatesPerDayData now properly updates reply rates for groups. Also fixed ForumReplyRatesDetailedReport which was not filtering thread starter replies. This was a bug fixed in 3.6, but now fixed in 3.7 as well.

24 October 2011: 3.7.342.20106

1 - Fixed an issue with ExtendedAnalytics that required modifying the ExtendedAnalytics.config file with an out of box install of a community site using a virtual directory.
6 - Added a script to create the EA table and sproc and correct file spelling.
9 - TotalMediaViewsPerGalleryReport now displaying "N/A" for most viewed file if there are no files in the gallery.
10 - External link was not working; decision was made to remove the external URL from this report. Note: It's available via the click-through.
13 - Fixed issue in RSS for a number of reports. For four of the reports, a fix to ReportBase (Line 994): (ContributionsPerUserReport, TotalRolesReport, TotalViewsPerWikiPageReport, UsersPerDomainDetailedReport). For the other report (ExceptionsDetailedReport), a SanitizeXML function was needed.
14 - Fixed an issue in UserTypesOneColumnByGroupReport - The CSV handler caused a yellow screen due to a missing Trend column. I added the Trend column to the query to ensure that it matched the visible report.
15 - Reverted the X-FRAME-OPTIONS change in order to get embedded reports working again.
16 - Added a coalesce and left join to make sure and include all views.
18 - Fixed an issue with ContributionsByUserByDateReport where the post title for blog comments was not showing up.
19 - Fixed an issue with ReplyRatesPerDayData task ignoring replies made to the first threads created in Evolution.
20 - Using HttpContext username to get a user instead of relying on reportParams.UserId.
22 - Changed Increment Update tasks to honor dates (previously they had pushed dates back 24hrs). See 3.6 Hotfix change 19037.
24 - Updated ForumPostData_Updates task to use checksum instead of 'top 1000' method, removed importId use as well.
25 - Fixed an issue where ForumThreadData_Updates task was not sorting the data it pulled and therefore would not eventually update all records. Also fixed performance issues with the task by removing the top 1000 limit; it now only updates records that need to be updated.
26 - Updated BlogCommentData_Updates merge task to remove 'top 1000' and add checksum method.
27 - BlogPostData Updates - Moved top 1000/checksum techniques from 3.6 to 3.7.
28 - Changed WikiData_Updates to IncrementalUpdateMergeQueryTask, and updated its query to remove top 1000 and to add a mergequery using checksum method 29 - WikiCommentData_Updates checksum/top 1000 fix.
30 - WikiRevisionData. Also fixed an issue in #6 where ImportDate was not honored.
33 - ImportDt = ImportDt minus 1 day 34 - UserFriendShipData Updates - As this task is nota merge task, the updates copy all the data over and then just update. It's simpler and faster to make the task non-incremental as this would bring all of the data over via BCP and skip the unneeded update step.
35 - Fixed an issue where GroupData_Updates task was not sorting the data it pulled and therefore would not eventually update all records. Also fixed performance issues with the task by removing the top1000 limit; it now only updates records that need to be updated.
35 - Fixed an issue where MediaCommentData_Updates task was not sorting the data it pulled and therefore would not eventually update all records. Also fixed performance issues with the task by removing the top 1000 limit; it now only updates records that need to be updated.
37 - Removed UserDisplayNameData_Updates task and changed UserDisplayNameData task to NonIncrementalQueryTask, the same change that was made in 3.6 hotfix.
38 - UserData Updates - Removed top 1000, removed < @ImportID and ensured that its using the same 3.6 Checksum technique.
40 - MediaPostData updates - Ported updates to MergeQuery section from 3.6 and removed top 1000 and @ImportID checks from the add'l queries.
42 - Removed 'top 1000' and added checksum comparison to the merge query for WikiPageData_Updates (same as in 3.6 hotfix).
43 - ReplyRatesPerDayData task RollupGroupId <> NULL for threads with no replies.
44 - Number 11 under Security Options starts with "specify" instead of "Specify" .
45 - Fixed an issue where UserFriendshipData task was not properly set up to run as a NonIncrementalTask. Needed to remove the top 1000 limit and the ImportIdField.
46 - Removed that Updates.sql and added a schema patch instead to remove the tasks.
47 - Corrected ReplyRatesPerDayData query where numerator and denominator values were switched.
49 - ReadMe spelling errors.
51 - Added logic to exclude Post and Wiki Drafts.
52 - RSSViewsReport are all zero, even though RSSs have been viewed.
54 - TheActiveUsersData task would not execute until all of its required tasks had executed at least once.
55 - Media Gallery RSS hit was not logged in te_WebAnalytics.

Telligent Analytics 3.6 hotfix notes

Jenny Jarrard — Thu, 19 Apr 2012 18:34:49 GMT

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 4/19/2012 1:34:49 PM

1 November 2011: 3.6.213.20277

11170 - Random new guid assigned to non-cookie users. There was a bug in the Extended Analytics module: The first time a user visited the site or used a new browser - or performed any action that called for a new cookie to be created - it used a random new guid instead of the user’s membership guid. After that user browsed the site, the second hit picked it up correctly - but the first one would never be correct. This applied to all authentication types. This was fixed.

1 June 2011: 3.6.213.17217

Fixed an issue with the External Links not properly building. Forums was missing SectionId and Media was missing ApplicationKey.
Fixed an issue where the MediaGalleryFilesByGalleryReport was not filtering by its @Param (Media Gallery).
Fixed an issue where the query calculated number of posts using SUM(PostId) instead of COUNT(PostId).
RegistrationsByDateReport uses GroupId to determine activity count (hence no "cannot scope by group" message), but does not filter users by Group (which is why the data seems off). Added the CanScopeToGroup property and set it to FALSE.
Fixed ForumReplyRatesDetailedReport from throwing an Excel export error. Updated query and table constructor to use new column name. Re: #1611.
Updated User Key Vital Signs report to use parameter sniffing and faster inner join queries (as opposed to IN > SELECT statements).
Reply Rate reports should not include one’s own reply to a thread.This was fixed.
Rewrote the AvgTimeToReply query to make it more performant
Updated the Update.SQL patch to rs_SchemaVersion from cs_.
MostViewedFilesByGalleryReport was not filtering by the selected date range control. This was corrected.

1 February 2011: 3.6.210.14528

Fixed a number of GroupPath errors. The external URLs were not formatting (or appearing in some cases) properly due to GroupPath not being selected.
- MediaActivityByDateReport
- MediaFileDownloadsPerDayReport
- MediaViewsByGalleryDetailedReport
- ActionsByModeratorReport
- ModeratorActionsAgainstUserReport
- ContributionsByUserByDateReport
- BlogSummaryReport
- PostsPerBlogPerDayDrillDownReport
- MediaGallerySummaryReport
- MediaCommentsByGalleryReport
- ViewsByContentByDateReport
- ContributionsByUserByDateReport
- MediaFilesPerMimeTypeDrillDownReport
- BuzzOverallSentimentReport (positive and negative reports)
Updated TaskStrings.config to avoid parameter sniffing for all of the TimeSlice tasks.
Changed TINYINT to INT column for csr_BlogPostData.
Fixed data display issue for TopBlogTopicsReport (variable named incorrectly).
Fixed timeout issue when scoping to CURRENT MONTH on the BlogsSummaryReport (arithmetic overflow issue).
Fixed data display issue with Most Viewed Blog Post (arithmetic overflow issue).
Ensured that double-byte characters always displaying correctly (update tasks setting columns using Column='Value' instead of Column=N'Value').

1. Full installation for release 3.7

Jenny Jarrard — Mon, 09 Apr 2012 20:15:46 GMT

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 4/9/2012 3:15:46 PM

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

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.

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)

If you are using IIS6 instead of IIS7, there are some differences to be aware of. This article details some critical differences.

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

1. Full installation for release 3.7

Jenny Jarrard — Mon, 09 Apr 2012 19:56:33 GMT

Revision 7 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 4/9/2012 2:56:33 PM

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

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)

If you are using IIS6 instead of IIS7, there are some differences to be aware of. This article details some critical differences.

In the [Telligent Evolution Site]>\Web.config file, locate the <modules> section in <system.webServer>. If you are using IIS7, uncomment the JavascriptAnalyticsHttpModule module line. If you are running IIS6, leave the line commented out.
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

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.

1. Full installation for release 3.7

Jenny Jarrard — Fri, 02 Mar 2012 21:10:33 GMT

Revision 6 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 3/2/2012 3:10:33 PM

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

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

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.

1. Full installation through release 3.6

Jenny Jarrard — Fri, 02 Mar 2012 21:09:35 GMT

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 3/2/2012 3:09:35 PM

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.

Tags: installation

1. Full installation for release 3.7

Jenny Jarrard — Fri, 17 Feb 2012 20:20:40 GMT

Revision 5 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 2/17/2012 2:20:40 PM

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

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

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.

Tasks

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

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 1/31/2012 10:04:48 AM

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:

About Web Analytics (3.5)

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

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 1/31/2012 9:59:10 AM

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

1. Full installation for release 3.7

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

Revision 4 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 1/18/2012 1:03:10 PM

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

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

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.

1. Full installation through release 3.6

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

Revision 27 posted to Telligent Analytics Product Documentation by Michael Kelley on 11/21/2011 3:29:54 PM

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.

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

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.

Tags: installation

1. Full installation for release 3.7

Jenny Jarrard — Wed, 16 Nov 2011 19:37:53 GMT

Revision 3 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 11/16/2011 1:37:53 PM

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

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

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.

1. Full installation for release 3.7

Jenny Jarrard — Wed, 16 Nov 2011 19:31:43 GMT

Revision 2 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 11/16/2011 1:31:43 PM

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

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.

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

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.

3.7 upgrade FAQ

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

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 11/16/2011 1:28:29 PM

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.

About Web Analytics 3.6 and 3.7

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

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 10/20/2011 3:46:49 PM

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.

3.7 upgrade FAQ

Jenny Jarrard — Fri, 14 Oct 2011 21:38:44 GMT

Revision 2 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 10/14/2011 4:38:44 PM

Q: Can I upgrade from Telligent Analytics 3.6 to Telligent Analytics 3.7?

A: No, it is not possible to upgrade from Telligent Analytics 3.6 to 3.7.

Q: If I want to upgrade my 5.x Telligent Evolution site to Telligent Community 6.0/Telligent Enterprise 3.0, do my 3.6 Analytics no longer work with my 6.0/3.0 site?

A: Telligent Community 6.0 and Telligent Enterprise 3.0 require Telligent Analytics 3.7, so once you upgrade, Telligent Analytics 3.6 won't work with the upgraded site.

Q: If I want to install Telligent Analytics 3.7, do I need to uninstall Telligent Analytics 3.6 first?

A: If you want to install 3.7, you must install it in a new location and point the Web site to that location in IIS. Then you will need to completely follow the installation instructions, including setting up Tasks via Analytics Runner. After 3.7 is installed, you can delete the 3.6 installation (provided you have a backup just in case).

How to delete 3.6

Tasks:

1. If you are using the Analytics Runner (versus the Tasks Service) via a scheduled job, point that job to the 3.7 version.
2. If you are using the Tasks Service, uninstall the service. You can reinstall the 3.7 version from the 3.7 folder; however, we recommend that clients use the Analytics Runner in 3.7 instead of the Tasks Service to process tasks.

Web files: Change the Web site in IIS manager to point to the 3.7 site.
Delete: After tasks and the Web site are not pointing to 3.6, you can remove the 3.6 installation by deleting it from the file system via Windows Explorer. Note: It is advised that you take a backup (i.e., a zip copy) and save it in case it's needed in the future.

Q: Is there any way to use the database files I have from 3.6 in 3.7?

A: No. The Anaytics data can't be reused, and needs to be reprocessed. We do include a script to clear out the data; however, unless there is a very compelling reason, you should create a new database for 3.7 from scratch.

How do I enable logging in my Task Service?

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

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 10/13/2011 1:34:45 PM

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.

Telligent Analytics Product Documentation

Telligent Analytics 3.7 hotfix notes

In this Article

16 May 2012: 3.7.342.24831

15 March 2012: 3.7.342.23287

22 February 2012: 3.7.342.22967

17 January 2012: 3.7.342.21980

28 November 2011: 3.7.342.20774

15 November 2011: 3.7.342.20509

24 October 2011: 3.7.342.20106

Telligent Analytics 3.7 hotfix notes

In this Article

16 May 2012: 3.7.342.24831

15 March 2012: 3.7.342.23287

22 February 2012: 3.7.342.22967

17 January 2012: 3.7.342.21980

28 November 2011: 3.7.342.20774

15 November 2011: 3.7.342.20509

24 October 2011: 3.7.342.20106

Embedding a report in an external Web page

Permissions

Telligent Analytics 3.7 hotfix notes

In this Article

15 November 2011: 3.7.342.20509

24 October 2011: 3.7.342.20106

Telligent Analytics 3.6 hotfix notes

In this Article

1 November 2011: 3.6.213.20277

1 June 2011: 3.6.213.17217

1 February 2011: 3.6.210.14528

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

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

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

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