Before installing a new community, ensure that you have met all the Preliminary requirements for installation.

This procedure applies to Telligent Community 6. The examples say "Telligent Evolution," but you should substitute in your own site's name where appropriate.

Installation notes

  1. If you open the Telligent Community zip file using Internet Explorer or Chrome, you may need to first right-click the.zip file and select Properties, then click Unblock if the option is available. Click OK to close Properties.
  2. If installing Telligent Community 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 community. In such cases, you will have to add <clear /> or <remove /> elements in your Community web.config file to remove the additions made in your parent web.config.
  3. If you set up your database to be case sensitive, you may experience future issues with names matching in sign-in or places that use a name on the URL to identify the location (groups, users, or blogs). See this article.
  4. The instructions for creating an application pool assume you're using IIS7. If you're using IIS6, see the Microsoft documentation.
  5. .NET framework version 4.0 is required for Telligent Community 6.
  6. If you are running Windows Server 2008 without SP2, you should install KB958854 to resolve some issues with .NET 4.0.  Windows Server 2008 SP2 and Windows Server 2008 R2 are unaffected by this issue.
  7. If you're using Windows XP for development purposes, your network service user is ASP.NET. If you're using Windows Server 2003, your network service user is NETWORK SERVICE. If you're using Windows Server 2008, your user is IIS APPPOOL\<application pool you create>.
  8. Search is required for Telligent Community 6.
  9. In Telligent Community 6, most tasks should be executed in their own Job Scheduler service.
  10. Job Scheduler's default user is NETWORK SERVICE. If you're using Windows Server 2008, you'll need to assign NETWORK SERVICE the same folder and database appropriate permissions you assign the service user.
  11. You need to access the site before starting Job Scheduler, because Job Scheduler relies on the site URI. If you don't access the site first, you can receive a background job error of "Invalid URI" error in the error log.
  12. In Telligent Community 6, Job Scheduler's logging is turned on by default.

    Obtain Telligent Community

    1. Obtain the installation package from Telligent Support.
    2. Extract the contents of the download to a temporary location on your hard drive (e.g., C:\inetpub\TempFolderUnzipBuild\ ).

    Installation components

    This installation procedure has been divided by installation area so that multiple administrators can install different aspects of a Telligent Community site.

    • Web server
    • Database server
    • Search server
    • Tasks server
    • Caching server

    Web server

    This procedure assumes you already have IIS installed, and have configured the Database and Search servers.

    Copy the files

    Create a Web directory folder and copy the files there:

    1. Create a path to hold the Telligent Community Web site (e.g., C:\inetpub\Telligent Evolution\). Note that the root folder path should be as short as possible to provide enough path space to the CFS.
    2. In the extracted .zip file folder, copy all of the zip file's web folder contents and paste them into the server's directory folder, leaving the directory structure intact.

    Create the Web site in IIS

    1. If you are using Windows Server 2003 or Windows Server 2008, create a new application pool. (If using Windows XP for development purposes, skip this step.)
      1. Open Internet Information Services (IIS) Manager.
      2. If required, connect to your Web server.
      3. In the Connections pane, 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 correct Net framework version is selected.


      7. Click OK.
    2. Create the IIS website.
      1. In IIS's left pane, navigate to Internet Information Services > [computer name] > Sites.
      2. Right-click  Sites, select Add Web Site....



        The Add Web Site dialog appears.

      3. Do the following:
        • Enter a name in the Site Name field (example: Telligent Evolution).
        • Select the application pool you created in Step 2.
        • Enter the path you created in Step 1 in the Physical path field (example: D:\Sites\Evolution\Web).
        • If you require the site to run on a specific IP address or port, enter those values into the  IP address and Port fields. 
        • Enter a value for the Host Name field for the host name you want the site to respond to (example: community.example.com).

      4. Click OK.
    3. 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 that your Web service is running under:
        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

    For further details on optimizing the performance of your Web server, see Web server and IIS configuration.

    Set file permissions

    1. Add the network service user to the permission structure. Then grant the Web site service account required file and folder permissions: read permissions to the web directory (which is the main directory for IIS) and modify permissions for web/filestorage/ and its sub-folders.
      1. Right-click the Telligent Community Web site folder and select Edit Permissions.



      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 above. Click OK.

      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.
      7. Repeat the above instructions, but this time assign rights for the web/filestorage folder instead of the Telligent Community Web site folder. In addition to Read, grant the service account Modify, Read & execute, List folder contents, and Write permissions.

         

    Configure the connectionstrings.config file

    You can't configure the connectionstrings file until after you create the database.

    1. Update connectionstrings.configin the Web site to point to the database on your database server.

      For assistance with connection strings, you can refer to   http://connectionstrings.com. (Telligent has no affiliation with the site.)

      Open the connectionstrings.config file in your Web site, and update the SiteSqlServer entry to point to the database.
      • If using Windows Authentication to connect to the database, the connection string should look something like:
        <add name="SiteSqlServer"
        connectionString="server=SERVERNAME;database=DATABASENAME;Trusted_Connection=yes;"
        />
      • If using SQL authentication, the connection string should look something like:
        <add name="SiteSqlServer" 
        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="SiteSqlServer"
        connectionString="server=(local)\SQLExpress;database=DATABASENAME;Trusted_Connection=yes;"
        />
        <add name="SiteSqlServer"
        connectionString="server=(local)\SQLExpress;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=yes;"
        />
    2. Check that you can access your Telligent home page.
      1. Open your Telligent URL.
      2. Check that the home page successfully loads without error.
      3. If an error occurs, check that you've followed the above steps correctly.

      This should only be a quick test - any functionality that requires search will not work yet.

    3. If you are hosting a site in a Web farm or if your Web application will be restarted frequently (such as under very strict and/or limiting memory requirements), add an entry for an explicit machine key to the web.config file under <system.web> in order to prevent viewstate decoding errors:
      1. Navigate to http://aspnetresources.com/tools/machineKey. This site generates a unique machine key.
      2. Place this entry within the <system.web> node of the web.config file.

    Configure the search URL

    Important: Solr should never be accessible to the public. Ensure that neither the Tomcat home page nor the Solr home page is publicly accessible. If this endpoint is accessible, work with your IT department or read  Securing Solr on Tomcat for more details on blocking this endpoint from the public.

    1. Ensure that all Web servers can access the Solr home page by opening to the Solr home page on each server ( e.g., http://<servername or localhost>:8080/solr/ ).
    2. Configure Telligent Community to use your Solr URL:
      1. Download the following communityserver_override.config file.
      2. Place this file in the root of your Web site directory.
      3. Find the following section in the communityserver_override.config file and replace PathToSolr with the URL to your Solr instance (e.g., http://localhost:8080/solr/).
        <Override xpath="/CommunityServer/Search/Solr"  
        mode="change"
        name="host"
        value="http://yourserver:XXXX/PathToSolr"
        />

      The Solr path URL is case-sensitive.

      Search won't work until you have Job Scheduler set up.

    Database server

    Create the database

    For further details on optimizing the performance of your database server, see Database Configuration and Database Maintenance.

    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 Evolution.) If needed, see Microsoft's instructional documentation for help.
    4. Click OK.

    Create schema

    Populate the database by executing the cs_CreateFullDatabase.sql script from the \SqlScripts\ 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 SqlScripts.
    3. Double-click cs_CreateFullDatabase.sql.  

    4. Select the database you created in step 1 of this Database section.
    5. Execute the query against the database.

    Create community

    Create the community by executing the cs_System_CreateCommunity stored procedure.

    1. In the SQL Server Management Studio toolbar, click New Query.



      This will open a blank tab in the right pane.
    2. Copy and paste the following script into the new query tab.

      EXECUTE[dbo].[cs_system_CreateCommunity]
      @SiteUrl = N'localhost/telligent_evolution'
      , @ApplicationName = N'telligent_evolution'
      , @AdminEmail = N'notset@localhost.com'
      , @AdminUserName = N'admin'
      , @AdminPassword = N'pa$$word'
      , @PasswordFormat = 0
      , @CreateSamples = 0

      where you specify the appropriate values for each parameter:

      • SiteURL: The path to your site. This should be the same path you expect to access your community with (e.g., localhost/telligent_evolution as in the script above, or Telligent Evolution in the examples we've been using above).
      • ApplicationName: Name of the application you created in IIS (e.g., N'Telligent Evolution as in the case of the examples we've been using above).
      • AdminEmail: The email address of the administrator of the site. (optional)
      • AdminUserName: Login username for the administrator. You can leave this blank if you are running the application on your local PC on a limited basis.
      • AdminPassword: Default password for the administrator. You can set this to whatever you would like to use as the password for the administrative user (you can leave this blank if you are running the application on your local PC on a limited basis). We strongly recommend you do NOT use the default password in your live site. (optional)
      • PasswordFormat: 0 to store the password in the database in clear text. This can be changed to encrypt the password after it is created. (optional)
      • CreateSamples: 0 if you do NOT want sample content, 1 if you want sample content created in your community. (optional)

    3. Select your database name from the database drop-down list on the toolbar.
    4. Click Execute.

    Once you have created your community, we recommend you create a new administrator account and delete the one you created when setting up your community. This is to ensure that your administrator account's password is encrypted in the database. (While it is possible to encrypt the administrator account's password when you create the community, you need to provide the hashed password for the @AdminPassword parameter, which starts getting more complicated than it's worth, given the easy workaround.)

    Create login and grant permissions

    1. If you have not already done so, create a login to your server.
      1. In SQL Server's Object Explorer pane, expand your server and then expand the Security folder.
      2. Right-click the folder and select New Login. The Login - New window appears.
      3. Enter the name of your service.

      4. Click OK.
    2. Create a login for your database.
      1. In SQL Server's Object Explorer pane, expand the database Security folder, then right-click Users and select New User. The Database User - New window appears.
      2. If you want Telligent Community to connect to the database via Windows Authentication, select General and then specify the  database login name as the username of the service account user determined above. If you want Telligent Community to connect to the database using SQL authentication, then specify any username in the Login name text box. 
        We recommend using Windows Authentication. If you want to use SQL authentication, make sure your SQL server supports mixed-mode authentication.

      3. Click OK.
    3. Grant the database login access to the Telligent Community database. (This is shown in the bottom of the previous screen capture.)
      1. In the bottom (Database role membership) pane, ensure only the following roles are checked:
        • aspnet_Membership_FullAccess
        • aspnet_Profile_FullAccess
        • db_datareader
        • db_datawriter
        • db_ddladmin 
      2. Click OK and close SQL Server Management Studio.

    Set up maintenance

    For this information, see Database maintenance.

    Search server

    Install Java

    Install Java on the search server. Remember that if you are using 64-bit Tomcat, you will need to use 64-bit Java.

    1. Test whether Java is already installed by viewing http://java.com/en/download/help/testvm.xml on the search server. In Telligent Community, search requires at least version 6 update 13. If your installation meets this requirement, skip to the Install Tomcat step below.
      • If you're using a 64-bit operating system, you must view this test page in a 64-bit browser (such as Internet Explorer 64-bit edition which comes pre-installed on all 64-bit versions of Windows).
    2. Download the latest version of java from http://java.com/en/download/index.jsp .

    Install Tomcat

    Install Tomcat. Remember that if you are installing 64-bit Tomcat, you need to match it with 64-bit Java.

    1. Download version 6 of the Tomcat Windows Service Installer (32-bit/64-bit Windows Service Installer, apache-tomcat-6.0.30.exe) from Apache. Take note of the following:
      1. In the Choose Components window, ensure you have selected the the Tomcat > Service and Tomcat > Native options.

      2. In the Choose Install Location window, make a note of the installation directory - this will be needed in the next step.


    2. Update Tomcat to support UTF8 characters:
      1. Open the /conf/server.xml file in the installation directory you selected in step b.B.
      2. Find the 8080 <Connector /> element in the server.xml file, and add the attribute uriencoding="UTF-8"
        <server>
        <service>
        <connector port="8080" uriencoding="UTF-8">
        ...
        </connector>
        </service>
        </server>
    3. Test that Tomcat is installed correctly by navigating to http://localhost:8080/.

    Set up Solr

    If you have any issues with search, see Troubleshoot search errors.

    1. Install Solr.

      If you want to run multiple Telligent communities from the same search server, follow the instructions at Host multiple Telligent Community communities on multiple Solr instances instead.

      1. Copy the Solr folder in the /Search/ directory of the Telligent Community install files to the root directory of Apache Tomcat (e.g., c:\Program Files\Apache Software Foundation\Tomcat 6.0).
      2. Copy the solr.war file in this folder to the /webapps directory of Apache Tomcat.
      3. Navigate to the Solr administration page (http://localhost:8080/solr/admin/) to verify that the installation was successful.

    Solr runs very well as configured out of the box. But if you have a medium to large-sized community, you should increase the memory allocated to the Java virtual machine (JVM). The default allocated memory is 64MB. You should consider giving it 512MB or more.
    To increase the memory for the JVM:
    1. Right-click the Tomcat Manager in the system tray and select Configure.
    2. Select the Java tab.
    3. Set the Maximum memory pool size (in MB) that you want to allocate to the JVM.

    Tasks server or Job Scheduler

    Make sure the Web site is up and running before proceeding with this step.

    Install the Job Scheduler

    1. Review the contents of the Telligent Community Suite package that contained the platform files used in the primary platform installation.  Inside the root of this archive should be a folder entitled (Tasks).
    2. Create a destination folder for the Job Scheduler.  We typically recommend C:\Program Files\Telligent\Job Scheduler\ (Program Files (x86) for 64-bit OSes).
    3. Copy all files from the installation directory of the package (step 1) into the folder created in step 2.
    4. Run install.bat as administrator (right-click the file and select Run as administrator) to install the Job Scheduler service.
    5. Copy your connectionstrings.config file from the Telligent Community site over the connectionstrings.config file in the Job Scheduler directory, or simply update connectionstrings.config there to point to your database.
    6. Copy your communityserver_override.config file from your Telligent Community site into the Job Scheduler directory. View the file and ensure that the filestorage location is correct. (If not, change the file to reflect the location.) If you do not have an override file, you need to create one from here and then update the location of the filestorage folder (value attribute below).
         <Override xpath="/CommunityServer/CentralizedFileStorage/fileStore[@name='Telligent.Evolution.Components.Attachments']"
             mode="change"
             name="basePath"
             value="c:\path\to\your\filestorage"
                   />
       <Override xpath="/CommunityServer/CentralizedFileStorage/fileStore[@name='Telligent.Evolution.Components.Attachments.Temporary']"
             mode="change"
             name="basePath"
             value="c:\path\to\your\filestorage"
                   />
       <Override xpath="/CommunityServer/CentralizedFileStorage/fileStore[@name='CommunityServer.Components.MultipleUploadFileManager']"
             mode="change"
             name="basePath"
             value="c:\path\to\your\filestorage"
                   />

      Notes: (1) Paths for CFS file stores should be updated to be absolute (i.e., full path and not using the ~/ prefix). (2) For this release, the filestore paths above show different namespaces. They are correct for each path.
    7. If you are using Windows Server 2008, you need to add the NETWORK SERVICE user to the web and filestorage folders with the same permissions and create a user for it in the server and database. (It may already exist in the server.)
    8. Open services (services.msc at the command prompt) and start the Telligent Job Scheduler service. The service should start automatically after the initial run. One way to verify that Job Scheduler is working is to confirm that search is indexing (by adding some content to the site and trying to search for a term it it, then receiving the correct response). If it is not working, refer to this article.

    Optional installations

    • Install Mail Gateway.
    • Set up a Caching Server

    • If you plan to use Telligent Analytics, perform the following steps. If you do not do so, you will not be gathering Web Analytics data.

    1. In your Telligent Community site's web.config file, locate the <modules> section in <system.webServer>. Uncomment the JavascriptAnalyticsHttpModule line.
    2. Locate the <handlers> section, and uncomment the analytics and analyticsUrls handlers.
    3. Optional: If your Telligent Community site is running on a Web farm, ensure that steps 1 and 2 occur on all Web servers.

    If you have trouble...

    Please refer to the Telligent Community Troubleshooting Guide.

    When starting the site...

    You may need to navigate to the Telligent license file from obtained from Support in order to add users, groups, and applications.