The CFS is configurable via a plugin. Is it Cfs Scripted Content Fragment Extension (core_v2_cfs) in core functionality?
Note: You should make any changes referenced in this section before you upgrade your Telligent Community Server site.
Community Server makes use of a Centralized File Storage (CFS) provider. CFS provides a great deal of flexibility to the developer or system administrator because it is relatively straightforward to configure Community Server to use any number of external file storage systems (Amazon's S3, UNC path, etc.). Community Server supports the concept of an overriding configuration file, so rather than changing the default install you can create an overrides file - communityserver_override.config. Here is an example that overrides the CFS to use a UNC path:
Note: The value for the xpath element should be on one line. Also, to properly override CFS, you would need to provide an override value for all of the CFS entries (of which the above is one example).
In this configuration, at least one of the nodes is accessing a resource (files) on another system (the one that hosts the UNC share). The security implications of cross-machine resource requests can be complicated. You can configure security parameters for your application a number of ways and each operating system uses a different account to run the ASP.NET process. There is a great matrix that shows you the various security contexts in which your resource request will leave the server.
Because many of these options are environment-specific, we encourage you to read about the various configurations that allow for impersonation and delegation in Community Server or any ASP.NET application. If you are switching from local file share to remote file share, you need to move all of the files and folders to the remote file share. You also need to review the file permissions once they are moved to the remote file share to ensure they are still accessible.
Understanding how the underlying ASP.NET security model works is critical to understanding how you must configure remote network file requests from within your application.
In the event centralized storage is undesirable, local storage on the Web nodes can be used. Available storage should be monitored closely. DFS can maintain file synchronization and should be monitored closely to ensure its health. To minimize the complexity of maintaining your communities Web nodes, the best practice is to ensure the local paths are identical across all nodes.
There are two keys to keeping authentication, authorization, roles and profile settings working correctly in a webfarm environment:
Cookie names: Ensure that cookie names set in the web.config file are the same on each node in the webfarm.
Machine keys: Ensure that the validationKey and decryptionKey values are the same on all nodes in the webfarm.
No. Solr runs independently from Community Server.
No. Solr only needs to be installed on one server. You can run Solr on a server that runs Community Server on a dedicated server. For Solr, if you have a large number of documents (> 1M documents) you should consider allocating a larger amount of RAM (2GB+) to Solr.
All web servers in the webfarm should be configured to point to the Solr instance. Edit the host attribute for the the Solr element of the communityserver_override.config file for all web servers. Example:
<Solr host="http://[yourSolrHost]:8080/solr" simpleSearchQueryType="dismax" enableFieldCollapsing="true" enableHighlighting="true">
Important: The Solr instance should not be accessible by the public and ideally only accessible by your web servers (and admins as necessary).
No. Indexing should be done in one of two ways:
Select one web server to run the indexing tasks. The SearchDeleteQueue and SearchIndex tasks should be enabled on this server and removed from all other web servers.