Telligent Evolution Platform

Forum Post: RE: Duplicate Emails

Billy — Fri, 10 Feb 2012 18:38:00 GMT

Emails are only in Job Scheduler.

-- The duplicate emails are very random also. It will not send duplicates out every time.

-- Am i correct assumeing that the service checks the DB email queue and if messages exist it sends them..

Sometimes for some reason the service does not believe it connected to the mail server and leaves the message in the queue and 2 minutes later on retry the message(s) are delivered for the second time.

Not sure if there is a place to allow for a longer time out before email message is considered failed or some other solution.

Thanks

Forum Post: Event Calendar with Enterprise 3.0 Theme

Chip Martin — Fri, 10 Feb 2012 16:34:00 GMT

Anyone done a Calendar Title widget for the Enterprise Theme in Enterprise 3.0?

Forum Post: Navigation Tab Address

Lisa Evans — Fri, 10 Feb 2012 13:07:00 GMT

I have an image link in my header that i have linked to a tab on the homepage, using plain html. The tab address keeps changing though. How do I link to a tab permanently?

Wiki: Telligent Enterprise 3

Anonymous — Thu, 09 Feb 2012 22:24:00 GMT

Wiki: Telligent Community 6

Anonymous — Thu, 09 Feb 2012 22:22:00 GMT

Wiki Page: Email Templates

Jenny Jarrard — Thu, 09 Feb 2012 18:03:00 GMT

In Telligent Evolution 5.6, the following templates have been moved from the Web/Languages folder to the Job Scheduler/Languages folder (as noted below) and need to be modified there instead:

forumpost_mailgateway.txt
forumpost_postnotification.txt
forumpost_threadnotification.txt
weblog_newpost.txt
weblog_newcomment.txt

All of the emails sent out by the Telligent Evolution platform can be customized, both in how they look and what information they contain.

In the email templates, tokens are used to specify information. When the email is sent, the tokens are replaced by the correct values they represent (i.e., $Subject -> "Subject of blog post").

All templates are listed below along with the tokens available to the template.

How to customize an email template:

Navigate to the email template folder, which for 5.0 or 5.5 can be found in the Web/Languages/<your language>/emails folder, and in 5.6 in the Job Scheduler folder - typically c:\program files\Telligent\Job Scheduler\Languages\<language>/emails.
Find the name of the template that you want to change/edit.
The templates are stored as .txt files. Thus to change the forumpost_threadmovenotification template, open forumpost_threadmovenotification.txt in any text editor.
The list of available tokens is given below (along with the Global Terms).

Global Terms

A list of terms that are available on all templates is available on the [[The global term tokens|Global tokens]] page.

Account notifications

forgottenpasswordwithtoken.txt message file

$forgottenpasswordurl - string - The URL where the user can change their password.
$ip - string - The IP host address of the remote client.
$user - [[The user token|User]] - The user who forgot their password.

newuser_accountcreated.txt messages file

$user - [[The user token|User]] - The user who created an account.

newuser_approved.txt messages file

$user - [[The user token|User]] - The user whose account was approved.

newuser_generatedpassword.txt messages file

$user - [[The user token|User]] - The user created an account with a generated password.

newuser_pending.txt message file

$user - [[The user token|User]] - The user who has attempted to join the site and is awaiting approval.

newuser_rejected.txt message file

$user - [[The user token|User]] - The user whose account was rejected.

roleemail.txt message file

$user - [[The user token|User]] - The recipient of the message, a member of the role.
$post - [[The post token|Post]] - The post containing the message for the user.
$roleName - string - The name of the role the message was sent to.

user_changedpassword.txt message file

$user - [[The user token|User]] - The user who change their password.

user_forgottenpassword.txt message file

$user - [[The user token|User]] - The user who requested to be sent a new password.

userinvitation.txt message file

$invitation - [[The user invitation token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the community.

userinvitation_withsection.txt message file

$invitation - [[The user invitation token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the section/group.

Blog notifications

weblog_feedbacknotification.txt message file

$parent - [[The post token|Post]] - The blog post given the feedback.
$post - [[The post token|Post]] - The new blog feedback, which may need approval.
$user - [[The user token|User]] - The user who subscribed to new comments.

weblog_moderationthreshold.txt message file

$section - [[The blog token|Blog]] - The blog that needs moderation attention.
$user - [[The user token|User]] - Blog owner who can moderate the blog.

weblog_newcomment.txt message file

$post - [[[The post token|Post]] - The new blog comment.
$user - [[The user token|User]] - The user who subscribed to new comments.

weblog_newpost.txt message file

$post - [[The post token|Post]] - The new blog post.
$user - [[The user token|User]] - The user who subscribed to new posts.

weblog_subscriptionconfirmation.txt message file

$section - [[The blog token|Blog]] - The subscribed blog.
$user - [[The user token|User]] - The user who has subscribed to the blog.

Contact notifications

contactform.txt message file

$appTitle - string - The name of the blog or group.
$body - string - The body of the message.
$email - string - The email address of the sender.
$link - string - The URL of the home page of the blog or group.
$name - string - The name of the sender.
$subject - string - The subject provided by the user.
$to - string - The email address of the owner of the blog or group.

contactform_usertouser.txt message file

$post - [[The post token|Post]] - The message being sent.
$user - [[The user token|User]] - The recipient of the message.

Forum notifications

forumpost_mailgateway.txt message file

$attachmentUrls - NameValueCollection - A collection of urls for attachments to the post.
$charSet - string - The email encoding to use.
$list - [[The mailing list token|MailingList]] - The mailing list that the post was sent to.
$mime.EncodeHeader(string subject, string charSet) - string - The encoded subject of the post.
$parentPost - [[The post token|Post]] - The parent post of the post that triggered the notification.
$post - [[The post token|Post]] - The post which triggered the notification.
$subscriber - [[The user token|User]] - The recipient of the notification.
$subjectCharSet - string - The email encoding to use for the subject.

forumpost_messageapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemoved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemovedandapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved and approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messageremoved.txt message file

$moderatedBy - [[The user token|User]] - The moderator who removed the post.
$post - [[The post token|Post]] - The post to the forum being removed.
$reason - string - The reason for the removal provided by the moderator.
$user - [[The user token|User]] - The author of the post.

forumpost_notifymoderators.txt message file

$user - [[The user token|User]] - The moderator who is being notified.

forumpost_notifythreadstarterofanswer.txt message file

$post - [[The post token|Post]] - The post which was marked as the answer.
$rejectAnswer - string - The url to reject the post as the answer.
$user - [[The user token|User]] - The user who posted the thread starter.

forumpost_notifythreadstarterofsuggestedanswer.txt message file

$currentUser - [[The user token|User]] - The user who verified the post as an answer.
$post - [[The post token|Post]] - The post which was verified as an answer.
$rejectAnswer - string - The URL to reject the answer.
$user - [[The user token|User]] - The user who posted the thread starter question.
$verifyAnswer - string - The URL to verify the suggested answer.

forumpost_postnotification.txt message file

$post - [[The post token|Post]] - The post which triggered the notification.
$user - [[The user token|User]] - The recipient of the notification.

forumpost_threadmovednotracking.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadmovenotification.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadnotification.txt message file

$post - [[The post token|Post]] - The post which started a new thread.-
$user - [[The user token|User]] - The user who subscribed to this thread.

Friendship notifications

followers_notification.txt message file

$follower - [[The follower token|Follower]] - The relationship of the follower.

friendship_approved.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested_nomessage.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

Group notifications

group_accessaccepted.txt message file

$group - [[The group token|Group]] - The group access has been granted to.
$user - [[The user token|User]] - The user being granted access.

group_accessrequest.txt message file

$group - [[The group token|Group]] - The group the membership request is for.
$message - string - The message provided by the user requesting access to the group.
$owner - [[The user token|User]] - The owner of the group.
$user - [[The user token|User]] - The user making the request for membership.

group_accessrequestdenied.txt message file

$group - [[The group token|Group]] - The group access has been denied to.
$user - [[The user token|User]] - The user being denied access.

group_useradded.txt message file

$group - [[The group token|Group]] - The group user has been added to.
$user - [[The user token|User]] - The user being added to the group.

Media Gallery notifications

mediagallerypost_commentnotification.txt message file

$parentPost - [[The post token|Post]] - The media gallery post the comment is for.
$post - [[The post token|Post]] - The comment to the media gallery post.
$user - [[The user token|User]] - The recipient of the comment notification.

mediagallerypost_newcomment.txt message file

Message notifications

group_messages_also_replied.txt message file

$message - [[The reply message token|Reply Message]] - The reply to the message thread.
$parent - [[The message token|Message]] - The first message in the conversation (the group message).
$recipient - [[The user token|User]] - The user that commented in the message thread.
$replies - [[The reply message token|Reply Message]] - The list of all replies to the parent group message.

group_messages_reply.txt messages file

$message - [[The reply message token|Reply Message]] - The reply to the parent group message.
$parent - [[The message token|Message]] - The first message in the conversation (the group message).
$recipient - [[The user token|User]] - The user the message who posted the status message.
$replies - [[The reply message token|Reply Message]] - The list of all replies to the parent group message.

messages_also_replied.txt message file

$message - [[The reply message token|Reply Message]] - The reply to the message thread.
$parent - [[The message token|Message]] - The first message in the conversation (the status message).
$recipient - [[The user token|User]] - The user that commented in the message thread.
$replies - [[The reply message token|Reply Message]] - The list of all replies to the parent status message.

messages_newconversationmessage.txt messages file

$conversation - [[The conversation token|Conversation]] - The conversation between the various participants.
$message - [[The message token|Message]] - The message in the conversation directed to the recipient user.
$user - [[The user token|User]] - The user the recipient of the message.

messages_newprofilecomment.txt messages file

$message - [[The profile message token|Profile Message]] - The comment on the profile.
$user - [[The user token|User]] - The user who received the comment (the profile's owner).

messages_reply.txt messages file

$message - [[The reply message token|Reply Message]] - The reply to the parent status message.
$parent - [[The message token|Message]] - The first message in the conversation (the status message).
$recipient - [[The user token|User]] - The user the message who posted the status message.
$replies - [[The reply message token|Reply Message]] - The list of all replies to the parent status message.

messages_spam.txt messages file

$message - [[The message token|Message]] - The message which has been marked as spam.
$messageUrl - string - The url of the activity message.
$spamScore - int - The score given to the message based on the spam rules.
$user - [[The user token|User]] - The recipient of the message.

messages_spam_deleted.txt messages file

$message - [[The message token|Message]] - The message which has been marked as spam.
$spamScore - int - The score given to the message based on the spam rules.
$user - [[The user token|User]] - The recipient of the message.

messages_spam_deleted_user.txt messages file

$message - [[The message token|Message]] - The message which has been marked as spam.
$user - [[The user token|User]] - The recipient of the message.

Wiki notifications

wikis_definitespam.txt message file

$page - [[The wiki page token|Wiki Page]] -The wiki page that has been flagged as possible spam.
$user - [[The user token|User]] - The user with permission to delete the wiki page to send the email to.

wikis_pageupdated.txt message file

$page - [[The wiki page token|Wiki Page]] - The updated wiki page.
$revision - [[The wiki page revision token|Wiki Page Revision]] - The previous version of the wiki page.
$user - [[The user token|User]] - The user who subscribed to updates to the wiki page.

wikis_possiblespam.txt message file

$page - [[The wiki page token|Wiki Page]] - The wiki page that has been flagged as possible spam.
$user - [[The user token|User]] - The user with permission to delete the wiki page to send the email to.

Customizing email replies to reply to the entire group whether you click Reply or Reply All

If upgrading to 5.x, you have the option of making all replies to a forum list go back to the entire group whether you click Reply or Reply all. This is a customization of the current 5.x behavior, which allows you to select replying to one member or replying all to the entire group.
1. Navigate to the email templates folder. For release 5.0 or 5.5, this will be in Web\Languages\<language>\emails\; for release 5.6 it will be in the Job Scheduler folder, which defaults to c:\Program Files\Telligent\Job Scheduler\, then continue to the \Languages\<language>\emails\ subfolder.)
2. Open forumpost_mailgateway.txt.
3. Under the line that begins with BCC:, add the following line:
```
Reply-To: <$globals.HtmlDecode($list.DetermineEmailAddress())>
```
  Setting the Reply-To will cause email clients to reply to the address listed instead of the address from which the email was sent.

Forum Post: User Banner Bug

bazqpr — Thu, 09 Feb 2012 17:51:00 GMT

Have noticed the very same bug on this site as well, click into your user profile pages, the user banner contains the link Update Profile, select any tab other than profile and the link remains, click on the link you know get the button to save profile without having any profile fields to edit, just the same user content you were viewing

Wiki Page: Install Telligent Enterprise

Jenny Jarrard — Thu, 09 Feb 2012 16:24:00 GMT

Installation notes

If you open the Telligent Enterprise 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.
If installing Telligent Enterprise 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 Enterprise web.config file to remove the additions made in your parent web.config.
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.
The instructions for creating an application pool assume you're using IIS7. If you're using IIS6, see the Microsoft documentation.
.NET framework version 4.0 is required for Telligent Enterprise 3.0.
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.
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>.
Search is required for Telligent Enterprise 3.0.
In Telligent Enterprise 3.0, most tasks should be executed in their own Job Scheduler service.
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.
In Telligent Enterprise 3.0, Job Scheduler's logging is turned on by default.

Obtain Telligent Enterprise

Obtain the installation package from Telligent Support.
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 Enterprise 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:

Create a path to hold the Telligent Enterprise 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.
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

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 [[supported software versions for servers, applications, and browsers|correct Net framework version]] is selected.
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 Add Application.
  
  The Add Application window appears.
3. Do the following:
  - Enter a name in the alias 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: C:\inetpub\Telligent Evolution).
4. Click OK.
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 configuration check-list|Web server and IIS configuration]].

Set file permissions

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

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;"
  />
```
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.
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.

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/ ).
Configure Telligent Enterprise 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.

Open SQL Server Management Studio and connect to your database server with an account that has sysadmin or dbcreator fixed server privileges.
Right-click Databases and select New Database. The New Database window appears.
In the Database name field, enter a name for the database. (Example: Telligent Evolution.) If needed, see Microsoft's instructional documentation for help.
Click OK.

Create schema

Populate the database by executing the cs_CreateFullDatabase.sql script from the \SqlScripts\ folder of the install package.

In SQL Server Management Studio, navigate to File > Open > File. The Open File dialog window appears.
Navigate to the temporary location where you unzipped the installation package and within that folder, to SqlScripts.
Double-click cs_CreateFullDatabase.sql.
Select the database you created in step 1 of this Database section.
Execute the query against the database.

Create community

Create the community by executing the cs_System_CreateCommunity stored procedure.

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

This will open a blank tab in the right pane.
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)
Select your database name from the database drop-down list on the toolbar.
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

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.
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 Enterprise 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 Enterprise 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.
Grant the database login access to the Telligent Enterprise 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.

Test whether Java is already installed by viewing http://java.com/en/download/help/testvm.xml on the search server. In Telligent Enterprise, 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).
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.

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

Install Solr.
If you want to run multiple Telligent communities from the same search server, follow the instructions at [[Host multiple Telligent Enterprise communities on multiple Solr instances]] instead.
1. Copy the Solr folder in the /Search/ directory of the Telligent Enterprise 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:

Right-click the Tomcat Manager in the system tray and select Configure.
Select the Java tab.
Set the Maximum memory pool size (in MB) that you want to allocate to the JVM.

Configure Telligent search for documents

On the server that runs the Job Scheduler, install either the Windows search service or indexing service - depending on your operating system.

Window Server 2008 / Windows Server 2008 R2 - Install the Windows search service:
1. Open the Server Manager: Navigate to Start > Run > ServerManager.msc.
2. In the Services tab, click Roles in the left pane and select Add Roles from the Roles Summary window. Alternatively, you can click the Action menu option and select Add Roles.
3. Continue with wizard and select the File Services check box. Click Next.
4. If not already checked, select the Windows Search Service check box and click Next. If either Windows Search Service or Indexing Service (under the Windows Server 2003 File Services) was already checked, you can cancel the installation; one of the necessary services is already installed.
  
  In the next option window, Select Volumes to Index for Windows Search Service. You do not need to select a volume. Click Next.
5. Click Install.
Windows Server 2003 / Windows Server 2003 R2 - Install the Indexing Service:
1. Navigate to the Windows Control Panel and select Add/Remove Programs.
2. Select Add/Remove Windows Components from the left pane of the Add/Remove window.
3. If not already checked, select the Indexing Service check box and click Next to install. If the check box was already checked, this indicates the service is already installed - so you can cancel the installation.
Windows Vista / Windows 7 - Ensure the Windows search service is installed:
1. Navigate to the Control Panel, click Programs, and then click Turn Windows features on or off.
2. If not already checked, select the Windows Search check box and click OK. If the check box was already checked, you can cancel the installation; the service is already installed.

Tasks server or Job Scheduler

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

All Telligent Enterprise 3.0 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.

Install the Job Scheduler

In release 3.0, the Job Scheduler is installed with a bat file rather than an msi. The instructions for installation are located in a README.txt file, and are reproduced here.

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).
Create a destination folder for the Job Scheduler. We typically recommend C:\Program Files\Telligent\Job Scheduler\ (Program Files (x86) for 64-bit OSes).
Copy all files from the installation directory of the package (step 1) into the folder created in step 2.
Run install.bat as administrator (right-click the file and select Run as administrator) to install the Job Scheduler service.
Copy your connectionstrings.config file from the Telligent Enterprise site over the connectionstrings.config file in the Job Scheduler directory, or simply update connectionstrings.config there to point to your database.

Copy your communityserver_override.config file from your Telligent Enterpirse 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"              />

Note: Paths for CFS file stores should be updated to be absolute (i.e., full path and not using the ~/ prefix).

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.)
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 [[Install the Mail Gateway|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.

In your Telligent Enterprise site's web.config file, locate the <modules> section in <system.webServer>. Uncomment the JavascriptAnalyticsHttpModule line.

Locate the <handlers> section, and uncomment the analytics and analyticsUrls handlers.

Optional: If your Telligent Enterprise 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 Enterprise Troubleshooting Guide.

Wiki Page: Install Telligent Community

Jenny Jarrard — Thu, 09 Feb 2012 16:22:00 GMT

Installation notes

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.
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.
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.
The instructions for creating an application pool assume you're using IIS7. If you're using IIS6, see the Microsoft documentation.
.NET framework version 4.0 is required for Telligent Community 6.0.
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.
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>.
Search is required for Telligent Community 6.0.
In Telligent Community 6.0, most tasks should be executed in their own Job Scheduler service.
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.
In Telligent Community 6.0, Job Scheduler's logging is turned on by default.

Obtain Telligent Community

Obtain the installation package from Telligent Support.
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 [[internet information services (iis) configuration|IIS installed]], and have configured the Database and Search servers.

Copy the files

Create a Web directory folder and copy the files there:

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

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 [[supported software versions for servers, applications, and browsers|correct Net framework version]] is selected.
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 Add Application.
  
  The Add Application window appears.
3. Do the following:
  - Enter a name in the alias 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: C:\inetpub\Telligent Evolution).
4. Click OK.
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 configuration check-list|Web server and IIS configuration]].

Set file permissions

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.

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;"
  />
```
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.
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

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

Open SQL Server Management Studio and connect to your database server with an account that has sysadmin or dbcreator fixed server privileges.
Right-click Databases and select New Database. The New Database window appears.
In the Database name field, enter a name for the database. (Example: Telligent Evolution.) If needed, see Microsoft's instructional documentation for help.
Click OK.

Create schema

Populate the database by executing the cs_CreateFullDatabase.sql script from the \SqlScripts\ folder of the install package.

In SQL Server Management Studio, navigate to File > Open > File. The Open File dialog window appears.
Navigate to the temporary location where you unzipped the installation package and within that folder, to SqlScripts.
Double-click cs_CreateFullDatabase.sql.
Select the database you created in step 1 of this Database section.
Execute the query against the database.

Create community

Create the community by executing the cs_System_CreateCommunity stored procedure.

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

This will open a blank tab in the right pane.
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)
Select your database name from the database drop-down list on the toolbar.
Click Execute.

Create login and grant permissions

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

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

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

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.

Right-click the Tomcat Manager in the system tray and select Configure.
Select the Java tab.
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

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).
Create a destination folder for the Job Scheduler. We typically recommend C:\Program Files\Telligent\Job Scheduler\ (Program Files (x86) for 64-bit OSes).
Copy all files from the installation directory of the package (step 1) into the folder created in step 2.
Run install.bat as administrator (right-click the file and select Run as administrator) to install the Job Scheduler service.
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.

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"              />

Note: Paths for CFS file stores should be updated to be absolute (i.e., full path and not using the ~/ prefix).

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.)
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 [[Install the Mail Gateway|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.

In your Telligent Community site's web.config file, locate the <modules> section in <system.webServer>. Uncomment the JavascriptAnalyticsHttpModule line.

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.

If you have trouble...

Please refer to the Telligent Community Troubleshooting Guide.

Wiki Page: Database configuration

Jenny Jarrard — Thu, 09 Feb 2012 16:18:00 GMT

SQL Server 2008 64-bit

SQL Server is a robust DBMS on any hardware, but given that 64-bit architecture is reasonable and readily available, we recommend that you use 64-bit hardware and of course the 64-bit versions of SQL Server for installations. This goes for both SQL Server 2005 and 2008. We recommend that you use SQL Server 2008.

Database disk I/O management

The database file system configuration is much more important than the Web server file system in terms of design. A system administrator needs to be concerned about the integrity of their disks, plan for easily expandable growth, have a good balance between disk reads/writes, and plan for system failure and recovery.

See Telligent's recommended database disk configurations for optimal database I/O performance.

Database memory

After the installation, consider adjusting the memory for the SQL Server Service. If you right-click the server (with SQL Server Manager), choose Properties and select the Memory tab. You can set the Maximum Server memory (in MB) as shown in the following screen shot.

We recommend that you allocate 80-85% of server memory for SQL Server. The optimal hardware configuration for the database is dedicated hardware with 16GB+ of memory.

We recommend that your services be dedicated to their own hardware; however, if your environment dictates that you have IIS and SQL Server running on the same machine, you will need to adjust these values accordingly. For a baseline the server needs 15-20% of the system RAM. Then split the RAM so 60% is used for SQL Server and up to 40% for IIS.

Collation

Server collation is the sort order and the case sensitivity of the data within the databases. Setting the collation at the installation time for the default collation of the databases is the best time. This is so that all of the system databases (master, msdb, model and tempdb) are created with the same sort order that the user databases would use. This allows for better interoperability.

If you use a case sensitive database, there might be issues with names matching in sign-in or places that use a name on the URL to identify the location (groups, users, or blogs).

Initial database size

The initial size of the database is very important. Planning the size of your community is not a one-time event: it should be evaluated at least once every six months.

We recommend that you plan for one year's growth when setting the initial database size - not only for the community's sake, but also for your file system. Even for smaller communities it is better to use a much larger introductory data file. For a lightweight community you should start with a 1GB data file size and 64MB log file size. Fewer expansions of the data files means that there are fewer file fragments on the hard disk. This is important for consistency at a raw file level.

Database sizing formula

Use the table below to approximate the total amount of storage required when sizing the disk space needed for your SQL Server database:

Feature / Capability	Storage Required
Users ^{see note}	3.04 kb
Roles	1 kb
Blog posts	45 kb
Blog comment	3 kb
Forum thread	4 kb
Forum reply	1 kb
Media	1.2 kb
Media comment	3 kb
Wiki page ^{see note}	45 kb
Wiki comment	3 kb
Metadata factor	12%

The formula assumes the default set of user profile properties and on average one revision of a wiki document.

The metadata factor % is a value that adds a percentage of the core data to the total size.

Sizing formula = (Number of Items * Item Storage Required) * 112%

For example, assuming 100,000 users at 3.04kb per-user, you would plan for 296.88MB of storage with an additional 35.6MB of metadata for a total storage requirement of 332.5MB.

Each configuration is unique. Some installations will have more user storage with custom user properties whereas other installations will have multiple revisions of Wiki documents.

Autogrowth SQL settings

Use the sizing recommendations in database sizing formula when creating your data file. There are two directions to take regarding autogrowth on SQL Server data and log files:

If your environment is consistent with monitoring the size of the data in the SQL files and the physical size of the files themselves, then there should be no autogrowth at all. At a minimum, sizing should be checked at least once a quarter and adjusted as least once every six months. This is the preferred direction.
If your environment is more lenient you can continue to set AUTOGROWTH in terms of megabytes. Start with 128 MB. This is a small enough value that it can grow with hardly any contention and you shouldn't have issues with getting "out of space" errors.

Recommendations

If you are space-confined, set your maximum file size so that you do not exhaust all available space on your disk. We recommend that you have a minimum of 40% free space on the disk. Anything less than 40% free could jeopardize any substantial database grow that may occur in the future.

For the database log file, take the same considerations into account. Transactions in Telligent Community are generally not very large, so you could size your log file much smaller such as, 64 MB or 128 MB. Your autogrowth could be set to something much smaller as well, such as16MB or 32 MB. You will find discussions on tracking growth later in this guide.

Database maintenance

Maintenance is not always considered when deploying a database; however, we have found that maintenance can be a critical component to maintaining the health of a database. As a general rule all tables with clustered indexes should be reindexed on a schedule. We recommend that you do this once a week. However, depending on your community's activity, you may want to do this once a month.

Telligent Community includes a number of database maintenance scripts.

Database reindex

We include the cs_system_dbreindex stored procedure in the Telligent Community codebase.cs_system_dbreindex can be scheduled (via a SQL Job) to reindex clustered indexes.

Table statistics

Table statistics should be updated on days that reindexing does not occur. Again, there is a stored procedure included in the Telligent Community codebase called cs_system_updatestatistics that can be scheduled for this purpose.

Database growth

We have also found that people generally do not track physical database and log growth over time. Tracking table and index growth over time gives you an idea of how fast your community is growing and can give you an idea of what your disk space needs will be.

Tracking physical database growth can be done with the SQL Server stored procedure sp_spaceused on a table-by-table basis. Additionally, the number of rows per table is a good metric. The number of rows per table provides you with the averages of the growth of your data over time within your community.

Database backups

We recommend that you schedule a single full-database backup once a week, a differential backup each day (not on full backup days), and log backups for the maximum recovery time you are allotted for your site.

For more information about backup options refer to:

http://msdn.microsoft.com/en-us/library/ms187510.aspx

For additional data about backup schedules refer to

http://vyaskn.tripod.com/sql_server_administration_best_practices.htm

Even though older versions of SQL Server are specified, the processes are the same.

Database tracing

The most effective way to determine problems within the database (related to performance) is through SQL Profiler. An exhaustive review of SQL Profiler can be found here.

Wiki Page: Database configuration

Jenny Jarrard — Thu, 09 Feb 2012 16:16:00 GMT

SQL Server 2008 64-bit

Database disk I/O management

See Telligent's recommended database disk configurations for optimal database I/O performance.

Database memory

We recommend that you allocate 80-85% of server memory for SQL Server. The optimal hardware configuration for the database is dedicated hardware with 16GB+ of memory.

Collation

If you use a case sensitive database, there might be issues with names matching in sign-in or places that use a name on the URL to identify the location (groups, users, or blogs).

Initial database size

The initial size of the database is very important. Planning the size of your community is not a one-time event: it should be evaluated at least once every six months.

Database sizing formula

Use the table below to approximate the total amount of storage required when sizing the disk space needed for your SQL Server database:

Feature / Capability	Storage Required
Users ^{see note}	3.04 kb
Roles	1 kb
Blog posts	45 kb
Blog comment	3 kb
Forum thread	4 kb
Forum reply	1 kb
Media	1.2 kb
Media comment	3 kb
Wiki page ^{see note}	45 kb
Wiki comment	3 kb
Metadata factor	12%

The formula assumes the default set of user profile properties and on average one revision of a wiki document.

The metadata factor % is a value that adds a percentage of the core data to the total size.

Sizing formula = (Number of Items * Item Storage Required) * 112%

For example, assuming 100,000 users at 3.04kb per-user, you would plan for 296.88MB of storage with an additional 35.6MB of metadata for a total storage requirement of 332.5MB.

Each configuration is unique. Some installations will have more user storage with custom user properties whereas other installations will have multiple revisions of Wiki documents.

Autogrowth SQL settings

Use the sizing recommendations in database sizing formula when creating your data file. There are two directions to take regarding autogrowth on SQL Server data and log files:

If your environment is consistent with monitoring the size of the data in the SQL files and the physical size of the files themselves, then there should be no autogrowth at all. At a minimum, sizing should be checked at least once a quarter and adjusted as least once every six months. This is the preferred direction.
If your environment is more lenient you can continue to set AUTOGROWTH in terms of megabytes. Start with 128 MB. This is a small enough value that it can grow with hardly any contention and you shouldn't have issues with getting "out of space" errors.

Recommendations

For the database log file, take the same considerations into account. Transactions in Telligent Enterprise are generally not very large, so you could size your log file much smaller such as, 64 MB or 128 MB. Your autogrowth could be set to something much smaller as well, such as16MB or 32 MB. You will find discussions on tracking growth later in this guide.

Database maintenance

Telligent Enterprise includes a number of database maintenance scripts.

Database reindex

We include the cs_system_dbreindex stored procedure in the Telligent Enterprise codebase.cs_system_dbreindex can be scheduled (via a SQL Job) to reindex clustered indexes.

Table statistics

Table statistics should be updated on days that reindexing does not occur. Again, there is a stored procedure included in the Telligent Enterprise codebase called cs_system_updatestatistics that can be scheduled for this purpose.

Database growth

Database backups

For more information about backup options refer to:

http://msdn.microsoft.com/en-us/library/ms187510.aspx

For additional data about backup schedules refer to

http://vyaskn.tripod.com/sql_server_administration_best_practices.htm

Even though older versions of SQL Server are specified, the processes are the same.

Database tracing

The most effective way to determine problems within the database (related to performance) is through SQL Profiler. An exhaustive review of SQL Profiler can be found here.

Forum Post: Select Tags

vlai — Wed, 08 Feb 2012 19:26:00 GMT

When writing a post, it seems that the max number of tags that "Select Tags" popup displays is 100. Is there a way to increase the number, or to choose which 100 tags to be displayed ourselves? We are using Telligent Community 5.6.

Forum Post: Mobile Version

ckuhlow — Wed, 08 Feb 2012 17:05:00 GMT

Does anyone have a mobile version of Telligent Community up and running that they could share? Besides the Telligent site that is. I'd be interested to see how others are using this module.

Forum Post: RE: Anti XSS implemented with $core_v2_page.GetFormValue

Alex Crome — Wed, 08 Feb 2012 16:51:00 GMT

Nope - it simply returns the raw form values..

Any validation for cross site scripting should be done before echoing user inputed data directly in the response (this can be done using the $core_v2_encoding.javascriptEncode(...) method)

Forum Post: RE: Migrating Forums from Drupal to Telligent

Patrick Mason — Wed, 08 Feb 2012 15:19:00 GMT

You should check with whatever medium is available support wise for Drupal on how to extract forum and user data from that system.

In terms of importing to Telligent Community the safest method is to take whatever medium you extracted to and import the data to your Telligent based community using the REST apis available.

http://telligent.com/community/developers/w/developer6/endpoint-documentation.aspx

Patrick Mason
Development Lead- Extensibility
o: 214.420.1329
telligent.com

From: Awais Kazimi [mailto:bounce-AwaisKazimi@communities.telligent.com]
Sent: Wednesday, February 08, 2012 9:14 AM
To: bugsandissues@communities.telligent.com
Subject: [Bugs and Issues - Telligent Community] Migrating Forums from Drupal to Telligent

Hi,

We are trying to migrate Drupal forums to Telligent platform. Surely, the database structure (and how information is stored) is different in the two platforms.

Is there any way to export drupal forums with users and taxonomies (and taxonomy access restrictions to users) to Telligent platform, so that our forum may be imported "as it is" to Telligent

Thanks

Wiki Page: Install and Configure Telligent Connect for Microsoft Lync

Jenny Jarrard — Wed, 08 Feb 2012 14:25:00 GMT

System requirements/prerequisites

Telligent Enterprise 3.0
Microsoft Lync Server 2010
Windows Server 2008 R2 64 bits
Microsoft .NET Framework 3.5 (for the service)
Microsoft .NET Framework 4 (for the Web server)
Microsoft C++ 2008 Runtime Redistributable x64

Installing the Windows Service

In order to display presence information for Telligent Connect for Microsoft Lync, you must first install and configure the Unified Communications Service on your application server. This service is a Windows service and should only be installed on a single server, preferably the server where your Telligent Job Scheduler is installed.

Obtain the installation package from Telligent Support.
Open the Extensions folder.
Open the TelligentConnectForMicrosoftLync zip file.
Open the Services folder.
From the installation package in the Services folder, execute TelligentUCServiceInstaller.msi.
Navigate to the installation folder (usually C:\Program Files\Telligent\Unified Communications Service).

Edit the Telligent.Enterprise.UC.CollaborationService.exe.configfile and alter the following settings according to the table:

<appSettings>      <!--      Lync Server Conectivity Information      The information below must be provided in order for the Service to      establish connections with Lync Server      -->      <add key="LyncServerFQDN" value="lync.server.domain.com"/>      <add key="LyncServerPort" value="5061"/>      <add key="ServiceSystemAccountSIPAddress" value="sip:username@domain.com"/>      <add key="ServiceSystemAccountDomain" value="domain"/>      <add key="ServiceSystemAccountName" value="username"/>      <add key="ServiceSystemAccountPassword" value="password"/>      <!-- Application Settings -->      <add key="LogFileName" value="Telligent Enterprise"/>      <add key="UCServiceLogSource" value="Unified Communications Service"/>      <add key="ClientSettingsProvider.ServiceUri" value=""/> </appSettings>

Key	Value
LyncServerFQDN	FQDN of Lync server (address)
LyncServerPort	Port for TLS communication with Lync server
ServiceSystemAccountSIPAddress	SIP-enabled account used by the service. The format of this is important. It should be sip:username@domain.com. For example, if you have a system account that is lyncuser@domain.com, you would enter sip:lyncuser@domain.com.
ServiceSystemAccountDomain	Domain name of service SIP account
ServiceSystemAccountName	Account name of service SIP account
ServiceSystemAccountPassword	Password of service SIP account
LogFileName	Windows Event Log file used by the service to write diagnostic information
UCServiceLogSource	Source name used by the service when writing to the log file

The service exposes its functionality to Telligent Enterprise using Web services. You can change the URL Telligent Enterprise uses to communicate to this service by altering the following line in the same file:
```
<add baseAddress="http://localhost:8732/TelligentUCServiceListener/service"/>
```
You would also have to alter this URL if your Web server and service are not running on the same machine.
In the same directory, locate the file installservice.bat and execute it as an Administrator (right-click, select Run as Administrator) to install the Windows service.
NOTE: This file assumes a path of "C:\Program Files\Telligent\Unified Communcations Service" as the installation path. If you installed into a different directory, you will need to edit the installservice.bat file and change the path to the Telligent.Enterprise.UC.CollaborationService.exe file before executing.
Depending on your architecture, you may need to open TCP port 8732, or whichever port you may have defined in step 4, in the Windows firewall on the installation server for both incoming and outgoing communications.
In Administrative Tools > Services, right-click the Telligent Unified Communications Service, select Properties, and set the start up option to Automatic.
Start the Telligent Unified Communications Service.

Installing into Telligent Enterprise

Once the service is configured and running, you will need to install the Telligent Enterprise Web files.

Always back up your files and database before installing anything into your Telligent Enterprise site.

Locate the Web folder in the installation package.
Copy the contents of the Web folder into your Telligent Enterprise site.

Within your Telligent Enterprise site, edit the web.config file located in the root and add the following information right before the closing </configuration>tag at the end of the file:

<system.serviceModel>      <bindings>         <basicHttpBinding>             <binding name="BasicHttpBinding_ITelligentUCServiceListener"                      closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00"                      sendTimeout="00:01:00" allowCookies="false" bypassProxyOnLocal="false"                      hostNameComparisonMode="StrongWildcard" maxBufferSize="65536"                      maxBufferPoolSize="524288" maxReceivedMessageSize="65536"                      messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"                      useDefaultWebProxy="true">                 <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"                       maxBytesPerRead="4096" maxNameTableCharCount="16384" />                  <security mode="None">                      <transport clientCredentialType="None" proxyCredentialType="None"                            realm="" />                      <message clientCredentialType="UserName" algorithmSuite="Default" />                  </security>             </binding>        </basicHttpBinding>     </bindings>     <client> 
       <endpoint address="http://localhost:8732/TelligentUCServiceListener/service"              binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_ITelligentUCServiceListener"              contract="CollaborationService.ITelligentUCServiceListener"              name="BasicHttpBinding_ITelligentUCServiceListener" />     </client> </system.serviceModel>

You will need to alter the endpoint element to the same URL you configured your service for in the service installation:

<endpoint address="http://localhost:8732/TelligentUCServiceListener/service"

Configuring Telligent Connect for Microsoft Lync

Currently, Telligent Connect for Microsoft Lync is only compatible with the Evolution2 theme of Telligent Enterprise 3.0.

To use the Telligent Connect for Microsoft Lync integration, you must first enable it and add the widgets to their respective places.

Enable the Telligent Connect for Microsoft Lync plugin:
1. Log into Telligent Enterprise as an Administrator.
2. Access the Control Panel, navigate to Site Administration, and select Manage Plugins.
3. Locate the Telligent Connect for Microsoft Lync plugin and enable it by selecting the check box.
4. Click Save.
Add the Lync Enabled Site User Links Widget to the header:
1. On the homepage, as an Administrator, select Edit Page, then Edit Header.
2. There are two Site - User Navigation Links widgets at the top of the header; remove the one on the left by clicking the X.
3. In the Widget search box, type Lync.
4. Replace the the widget you just removed with the Lync Enabled Site User Navigation widget.
5. Change the border options to No Wrapper with No Spacing.
6. Click the pencil icon to configure the widget. Disable all the items except Browse Groups, Favorite Places, and Lync Chat. Save the configuration.
7. Lock the widget by clicking the padlock icon in the header.
8. Save the header, then save the page, choosing it as the new default.
Add the Lync Enabled User Hover Widget to the footer:
1. On the homepage, as an Administrator, select Edit Page, then Edit Footer.
2. Remove the User-Hover widget by clicking the X in the header.
3. In the Widget search box, type Lync.
4. Place the Lync Enabled User Hover in the same place where you removed the User-Hover widget.
5. As with the previous widget, adjust the border options to No Wrapper with No Spacing.
6. Save the footer, then the page, making it the new default version.
Add the Lync Enabled User Banner Widget to the user profile page:
1. As an Administrator, navigate to your profile page.
2. Select Edit Page.
3. Type Lync in the widget search box.
4. Replace the User- Banner widget with the Lync Enabled User Banner widget.
5. As before, change the border options to No Wrapper With No Spacing.
6. Save the page.

Wiki Page: Telligent Connect for Microsoft Lync Guide

Jenny Jarrard — Wed, 08 Feb 2012 14:24:00 GMT

This guide contains installation and configuration instructions for Telligent Connect for Microsoft Lync.

Forum Post: RE: Change archived posts 'RSS Post Excerpt Size'

Patrick Mason — Wed, 08 Feb 2012 14:13:00 GMT

All hotfixes should be obtained via support

Patrick Mason
Development Lead- Extensibility
o: 214.420.1329
telligent.com

From: Leo [mailto:bounce-LeoNel@communities.telligent.com]
Sent: Tuesday, February 07, 2012 9:53 PM
To: bugsandissues@communities.telligent.com
Subject: RE: [Bugs and Issues - Telligent Community] Change archived posts 'RSS Post Excerpt Size'

Anyone have the download for May, 2011 Hot Fix Release?

Forum Post: RE: 6.0 Installation.

Praful Memane — Wed, 08 Feb 2012 08:37:00 GMT

There was a similar problem reported and a reason provided by Alex Crome telligent.com/.../1355083.aspx

Forum Post: RE: Link to a theme stylesheet for a modal popup that uses a velocity macro for the modal content source

Michael Monteleone — Tue, 07 Feb 2012 21:46:00 GMT

For this scenario, I would recommend instead to use

$core_v2_page.RenderThemeHeaders("%{ IsModal = true/false }") within your <head> tag in your modal dialog velocity callback.

This will render theme-defined CSS, Javascript, and other headers along with any headers registered through $core_v2_page (AddLink, AddMeta, SetTitle, etc) and common javascript (jQuery, jQuery validate, GLOW, and Evolution jQuery plugins). It specifically includes stylesheets defined by the theme for use in modals.

Hope this helps.

Telligent Evolution Platform

Forum Post: RE: Duplicate Emails

Forum Post: Event Calendar with Enterprise 3.0 Theme

Forum Post: Navigation Tab Address

Wiki: Telligent Enterprise 3

Wiki: Telligent Community 6

Wiki Page: Email Templates

In this Article

How to customize an email template:

Global Terms

Account notifications

forgottenpasswordwithtoken.txt message file

newuser_accountcreated.txt messages file

newuser_approved.txt messages file

newuser_generatedpassword.txt messages file

newuser_pending.txt message file

newuser_rejected.txt message file

roleemail.txt message file

user_changedpassword.txt message file

user_forgottenpassword.txt message file

userinvitation.txt message file

userinvitation_withsection.txt message file

Blog notifications

weblog_feedbacknotification.txt message file

weblog_moderationthreshold.txt message file

weblog_newcomment.txt message file

weblog_newpost.txt message file

weblog_subscriptionconfirmation.txt message file

Contact notifications

contactform.txt message file

contactform_usertouser.txt message file

Forum notifications

forumpost_mailgateway.txt message file

forumpost_messageapproved.txt message file

forumpost_messagemoved.txt message file

forumpost_messagemovedandapproved.txt message file

forumpost_messageremoved.txt message file

forumpost_notifymoderators.txt message file

forumpost_notifythreadstarterofanswer.txt message file

forumpost_notifythreadstarterofsuggestedanswer.txt message file

forumpost_postnotification.txt message file

forumpost_threadmovednotracking.txt message file

forumpost_threadmovenotification.txt message file

forumpost_threadnotification.txt message file

Friendship notifications

followers_notification.txt message file

friendship_approved.txt message file

friendship_requested.txt message file

friendship_requested_nomessage.txt message file

Group notifications

group_accessaccepted.txt message file

group_accessrequest.txt message file

group_accessrequestdenied.txt message file

group_useradded.txt message file

Media Gallery notifications

mediagallerypost_commentnotification.txt message file

mediagallerypost_newcomment.txt message file

Message notifications

group_messages_also_replied.txt message file

group_messages_reply.txt messages file

messages_also_replied.txt message file

messages_newconversationmessage.txt messages file

messages_newprofilecomment.txt messages file

messages_reply.txt messages file

messages_spam.txt messages file

messages_spam_deleted.txt messages file

messages_spam_deleted_user.txt messages file

Wiki notifications

wikis_definitespam.txt message file

wikis_pageupdated.txt message file

wikis_possiblespam.txt message file

Customizing email replies to reply to the entire group whether you click Reply or Reply All

Forum Post: User Banner Bug

Wiki Page: Install Telligent Enterprise

In this Article

Installation notes

Obtain Telligent Enterprise

Installation components

Web server

Copy the files