Telligent periodically makes new releases available to users to enhance the Telligent platform and application functionality. To upgrade an existing installation you will need to upgrade the site's database as well as its Web files. Therefore the instructions have been divided into these areas where action is required. Please note that it is highly recommended to perform the upgrade in a test environment first before upgrading a live site.
If you have a pre-existing Community Server Evolution (CSE) or Telligent Enterprise installation, you can complete the following processes to upgrade to Telligent Enterprise 3.x.
Unblock the zip package by right-clicking it and navigating to Properties. If there is an Unblock button at the bottom of the Properties window, click it to unblock the zip. If there is no Unblock button, the zip is already unblocked.
If you want to upgrade from Telligent Event Calendar 1.7 to Telligent Event Calendar 20 (both of which are compatible with 3.0 and 3.1), you can simply overlay the files from the 2.0 install over your 1.7 site files and then run the 2.0 SQL script.
Instructions for updating Mail Gateway (only if installed and the folder is present in the package)
When upgrading from release 2.0 or later, default pages are not deleted or reverted to factory defaults. This requires either (a) reverting all theme pages via the Revert button in the Site Administration Control Panel or (b) manual editing of every page to ensure it looks satisfactory.
If you are upgrading from 2.5.6 to 3.x, you will need to remove the earlier version and install Telligent Job Scheduler for 3.x.
Validate the number of servers configured to access your existing Telligent Enterprise database. To do this:
If there is a discrepancy between the number of licensed servers versus those currently in use, you will receive licensing error messages and will have some trouble upgrading Telligent Enterprise. In the event of a difference, you can check to see whether you have old servers registered in the Manage Licenses page. Then you can contact Support to resolve the issue.
Obtain the installation package from Customer Care.
If you are opening the package using Internet Explorer, you may need to unblock the package:
Open the folder to which you downloaded the package.
Right-click the package and select Properties.
At the very bottom of the screen that window, you may see an Unblock button. If you see this, click Unblock.
Extract the contents of the package to a temporary location on your hard drive.
If you have customizations to your site's files, read the next section (Update theme customizations). Otherwise, progress to upgrading website files.
Ensure you back up the entire site to another folder beforehand. If you are upgrading the same website's files and not creating a new site, perform most of these instructions on the original site's Web folder.
Copy the upgrade Web folder into a new folder.
Install an application pool if you have not already done so.
Change your ASP.NET version from below version 2 to 4 if you have not already done so.
Grant your service user read permission on c:\<local directory, such as inetpub>\<web folder>.
Grant the service user modify permission on C:\<local directory, such as inetpub>\<web folder>\filestorage .
Update the connectionStrings.config file in the <web folder> to point to the database the site is using (if you are not upgrading the same database). Reference the connectionStrings.config file from the site's backup if necessary.
Update the folder path for the site's entry in IIS so that it points to the new folder (if you are not upgrading the same folder), for example C:\<local directory, such as inetpub>\<web folder>. If you are using IIS6 instead of IIS7, refer to the Microsoft IIS 6 documentation for your specific platform.
Don't test the website URL until after you upgrade the database. You may run into Windows Authentication issues if you do so prematurely, and some sprocs may be missing until that point.
Back up your database.
Inside the extracted contents of the upgrade package, open the SqlScripts folder.
There are several SQL files in the SqlScripts folder. Use SQL Server Management Studio to open the cs_UpdateSchemaAndProcedures.sql script file.
Execute the file against the database that your site is referencing. Ensure that the query returns a successful result. Don't run any of the other queries unless instructed to do so by Support.
If you are using Windows Authentication with Telligent Enterprise, update the communityserver_override.config file.
Test the upgraded site by visiting the site's URL in a browser. If the site doesn't work, double-check the service user ID, its assigned rights, and the connectionstrings.config file.
When you upgrade from 2.x to 3.x, run the following page as an administrator. (Do this after the database and Web files have been updated.)
If files (css, images, etc.) are uploaded to a site, group, or blog theme via theme configuration in the Control Panel, those theme files were previously stored in a specific directory in CFS. In 3.x, that location is slightly different (as theme names changed to GUIDs in 3.x), so this script moves those files from where they would have been to the new location. This tool does not create new themes or migrate existing themes from 2.x to 3.x.
Install your Telligent Enterprise 3.x license at this point and test it by updating your connectionstrings.config file and trying to navigate to the site. If you do not install your license, you could get a yellow screen.
Perform the following steps on the server that is running Solr:
The following instructions assume the Solr home ([solr home]) directory is in the default installation location, e.g., c:\Program Files\Apache Software Foundation\Tomcat 3.0\solr. If you have changed the home directory for Solr, adjust the instructions accordingly.
If you've made any customizations to the schema.xml file or solrconfig.xml file, you should use a merge tool such as WinMerge and merge the custom changes to the updated files.
If using Mail Gateway with Telligent Enterprise 2.x, you need to take some additional steps during the 3.x upgrade to also upgrade Mail Gateway (if you're using it; if you're not, skip this section).
In Telligent Enterprise 3.x, most tasks should be executed in their own service.
All Telligent Enterprise 3.x sites need to install the Telligent Job Scheduler. To learn more about working with custom tasks in the Job Scheduler, see the article in the Developer documentation.
Note that if you have Job Scheduler for Enterprise 2.x, it needs to be uninstalled, and then you need to install the Job Scheduler Telligent Evolution 6.x/Telligent Enterprise 3.x version.
In Telligent Evolution release 6.x/Telligent Enterprise 3.x, the Job Scheduler is installed with a .bat file rather than an msi. The instructions for upgrade are located in a README.txt file, and are reproduced here.
If you still have any problems after following the troubleshooting suggestions provided in the documentation, please contact Support.
Telligent Systems, Inc. ©2013, All Rights Reserved