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.
This installation procedure has been divided by installation area so that multiple administrators can install different aspects of a Telligent Community site.
This procedure assumes you already have IIS installed, and have configured the Database and Search servers.
Create a Web directory folder and copy the files there:
For further details on optimizing the performance of your Web server, see Web server and IIS configuration.
You can't configure the connectionstrings file until after you create the database.
For assistance with connection strings, you can refer to http://connectionstrings.com. (Telligent has no affiliation with the site.)
<add name="SiteSqlServer" connectionString="server=SERVERNAME;database=DATABASENAME;Trusted_Connection=yes;" />
<add name="SiteSqlServer" connectionString="server=SERVERNAME;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=no;" />
<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;" />
This should only be a quick test - any functionality that requires search will not work yet.
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.
<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.
For further details on optimizing the performance of your database server, see Database Configuration and Database Maintenance.
Create a new database in SQL Server.
Populate the database by executing the cs_CreateFullDatabase.sql script from the \SqlScripts\ folder of the install package.
Create the community by executing the cs_System_CreateCommunity stored procedure.
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 = Nemail@example.com' , @AdminUserName = N'admin' , @AdminPassword = N'pa$$word' , @PasswordFormat = 0 , @CreateSamples = 0
where you specify the appropriate values for each parameter:
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.)
For this information, see Database maintenance.
Install Java on the search server. Remember that if you are using 64-bit Tomcat, you will need to use 64-bit Java.
Install Tomcat. Remember that if you are installing 64-bit Tomcat, you need to match it with 64-bit Java.
<server> <service> <connector port="8080" uriencoding="UTF-8"> ... </connector> </service></server>
If you have any issues with search, see Troubleshoot search errors.
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.
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.
Locate the <handlers> section, and uncomment the analytics and analyticsUrls handlers.
Optional: If your Telligent Community site is running on a Web farm, ensure that steps 1 and 2 occur on all Web servers.
Please refer to the Telligent Community Troubleshooting Guide.
Telligent Systems, Inc. ©2013, All Rights Reserved