Table of Contents
- Initial setup
- Running the initial data load
- Enable the widgets on the Telligent Evolution site
- A note about multiple version of SSIS
TelligentAnalytics40-22.214.171.124-Community9 is compatible with Evolution 9.x.
TelligentAnalytics40-126.96.36.199-Community10 is compatible with Evolution 10.x.
- Download the Telligent Analytics 4.1 package.
- Right-click the package and select Properties. If you see an Unblock button, click it and then click Save. If you do not see the button, this indicates that the package is already unblocked.
- From the package Evolution folder, copy both Telligent.Analytics.dll and PostSharp.dll into the Web/bin folder of your Telligent Evolution site.
- In SQL Server Management Studio, run the evo_addAnalyticsSprocs.sql script located in the package Evolution folder on your Telligent Evolution 7.1, 7.5, or 8.x database.
- In SQL Server Management Studio, create a new database.
- Add the user Network Services to the Security folder of the database.
- Assign the permissions ddladmin and dbadmin to the user.
- Note the name of the database.
- Run the analytics40_createSchema.sql script located in the package Analytics folder on the new database.
- Set the timezone offset for the reports. By default report data is stored in GMT (0 offset). To change this execute the following SQL, replacing "-6" with your offset. The example below is setting the timezone offset for Central CST.
exec Update_TimezoneOffset -6
Note: You must set this during installation time if you want report dates to reflect your core timezone.
- Open your Telligent Evolution site Web/connectionstrings.config file in a text editor as admin.
- Add the following string to the file, replacing "Telligent Analytics" with the name you set for the Analytics database and (local) with your database server:
<add name="TelligentAnalytics" connectionString="server=(local);uid=;pwd=;Trusted_Connection=yes;database=Telligent Analytics" />For example, after you have added this string to your existing Telligent Evolution Web/connectionstrings.config file, it would look something like the following file:
<?xml version="1.0" encoding="utf-8"?> <connectionStrings> <add name="SiteSqlServer" connectionString="server=(local)\SQLExpress;uid=;pwd=;Trusted_Connection=yes;database=TelligentCommunity70" />
<add name="TelligentAnalytics" connectionString="server=(local)\SQLExpress;uid=;pwd=;Trusted_Connection=yes;database=Seven40" /> </connectionStrings>
- Open the ConnectionStrings.dtsconfig file in the package Analytics folder using a text editor such as Notepad or Notepad++ (as admin).
- Find the line that says
<Configuration ConfiguredType="Property" Path="\Package.Connections[TelligentAnalytics].Properties[ConnectionString]" ValueType="String"> <ConfiguredValue>Data Source=(local);Initial Catalog=TelligentAnalytics;Provider=SQLNCLI10.1;Integrated Security=SSPI;</ConfiguredValue> </Configuration>and replace the highlighted text (Initial Catalog=TelligentAnalytics) with the name of your Telligent Analytics database as well as replacing (local) with your database server.
- In the same file, find the line that says
<Configuration ConfiguredType="Property" Path="\Package.Connections[TelligentEvolution].Properties[ConnectionString]" ValueType="String">and replace the highlighted text (Initial Catalog=TelligentEvolution) with the name of your Telligent Evolution database and (local) with your database server.
<ConfiguredValue>Data Source=(local);Initial Catalog=TelligentEvolution;Provider=SQLNCLI10.1;Integrated Security=SSPI;</ConfiguredValue>
- Save your changes.
- On the server that will be executing the SSIS package, copy the contents of the Analytics folder to a final location where you will store this pacakge - ex. "D:\TelligentAnalytics\".
- Open the Windows Server 'Task Scheduler' management UI and select "Create Task".
- Give the task a name, ex. "Telligent Analytics Data Update" and select "Run whether user is logged on or not". Note: If using integrated security to connect with SQL Server, verify the account running the task has access to the database.
- Select the "Actions" tab and click "New", "Start a Program". In the "Program/script" value, set "etl.cmd" and in the "Start in" value, set the patch that contains the SSIS package, ex. "D:\Telligent Analytics".
- Next, configure the schedule. Select the "Triggers" tab and select "Daily". Configure the start time (ex. 6 AM).
- Save the task.
After setting up the task, its recommended you run the initial data load. The initial data load will typically take more time and query the Evolution more frequently than subsequent runs so you may want to do this during off-peak hours.
- On the server that has the scheduled task setup, open the "Task Scheduler" management UI.
- Right-click on the newly created Analytics task and select "Run".
- Wait for the task to complete and upon completion, confirm the last few lines in the log file reads "The package returned DTSER_SUCCESS (0)".
- You have successfully completed and configured the Analytics ETL job.
- Log into Telligent Evolution as admin.
- Navigate to Control Panel > System Administration > Site Administration > Site Configuration > Manage Plugins.
- Locate the Telligent Analytics plugin and select the check box.
- Click Save.
- Navigate to Control Panel > System Administration > Site Administration > Widget Studio > Enable/Disable widgets.
- Enable all Analytics 4.1 widgets for the Dashboards, Groups, Sitewide, and Blogs themes - for each of the Analytics 4.1 widgets, on each theme tab:
- Select the widget in the Not Allowed Widgets column. Click the > to move it to the Allowed Widgets column.
- Click Save on each theme tab.
- Test the widget installation by clicking Edit Page on a page and adding the widget, then clicking Save Page.
Telligent Analytics is able to work with either SQL 2012, SQL 2014 or SQL 2016. Whichever version you are using, use the files in the corresponding folder in the release package (e.g. if you are using SQL 2014, then use the files in the 2014 folder).
If you have multiple versions of SSIS installed, then you need to edit the etl.cmd file to provide the full explicit path to dtexec.exe in the version of SQL that you want to use. For example, if you want to use SQL 2012, then you need to edit to contents of etl.cmd so that it looks something like:
"C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\dtexec.exe" /F "TelligentAnalyticsETL.dtsc" ...etc
The full path will vary based on what drive/folder to which you've installed SQL Server and which version you want to use, so the above is only an example.
If you only have one of version of SSIS installed, then you don't need to make this edit, as dtexec.exe is in the path, and there will be no ambiguity.