This page describes how to set up Communifire version 4.5 and above on your own server. This document includes the following sections:
When you run a server-side application, you should also have a daily backup solution for the database and the entire directory where Communifire is installed. Manual backups are not unheard of (believe it or not), but automatic backups are always optimal. If you are questionable about backups, please let us know ... we can advise, we see this everyday.
To give you an idea of Communifire's RAM consumption, here are some cases that show the amount of RAM required with respect to the number of users (this does not include the RAM and CPU usage of the database but only the memory used by the Communifire IIS app):
NOTE: Communifire is an extremely fast software application. In 99% of circumstances, you will have no issues with speed. If you have 1,000,000 users or more, you're going to need a custom solution ... so talk to us and we can help you decide on a server infrastructure.
Communifire is a modern web application that uses HTML5 and CSS3 elements for enhanced usability on desktop computers as well as a very vast array or mobile devices. Not all browsers are considered "modern" by the community, and not all browsers support and allow such elements. For example, we use an advanced technology called SignalR (latest long-polling technology from Microsoft), which allows us to send updates to the browser without page refreshes. Unfortunately, SignalIR does not fully work with IE8 (please upgrade to the latest and most technological advanced browsers.) If you're using IE8, your users may not be able to fully experience Communifire's rich features in their entirety. Also, the online document viewer, which uses HTML5, will not work on IE8 as IE8 is not HTML5 friendly.
Communifire is supported to work on the web browsers below:
Download the Communifire installation files as a .rar or .zip file from My.Axero files section. You must purchase a license before being granted access to download the installation files.
NOTE: Per your request, customers on active support can be provided a Visual Studio project. This often makes it easier for you to modify and publish the project files (User Interface, CSS, HTML, etc.) from within the Visual Studio environment.
Unzip the installation file to a local directory and follow the steps mentioned below:
EXEC [Dyve_System_InstantiateCommunity] @ApplicationName = 'Your_app_name_goes_here',
@ApplicationURL = 'http://www.your-application-url.com',
@VirtualDirectory = '', @DefaultEmailAddress = 'email@example.com',
@SMTPServer = '', @SMTPUsername = '', @SMTPPassword = '', @SMTPPort = 25,
@AdminUserName = 'admin', @AdminPassword = 'admin'
NOTE: If you are installing CF as a virtual directory, please make sure that you add a forward slash ("/") before the virtual directory name. For example, for "http://your-site.com/community", set the @ApplicationURL='http://your-site.com' and the virtual directory name would be passed as follows: @VirtualDirectory = "/community".
After configuring your database & web server, go to the unzipped Communifire installation files (same files as in step 2) and change the connection string in the CFConnectionStrings.config file so that it reflects the credentials of your Communifire database.
Now you need to copy-paste these Communifire installation files to the folder which is set as a website/application in your IIS.
Make sure the application pool uses .NET 4.0, Enable 32-bit applications = true, Idle Timeout of the application pool is set to 0, Disable Overlapped Recycle = true, Regular Time Interval = 41760. To change these settings, open IIS Manager, go to Application Pools, select your application pool and click Advanced Settings. Refer this screen shot below for these two settings:
<system.net> <defaultProxy enabled="true"> <proxy bypassonlocal="true" proxyaddress="http://your proxy address here:8080/" /> </defaultProxy> </system.net>
<system.web> <httpRuntime maxRequestLength="2000000" executionTimeout="100000" /> </system.web>
<security> <requestFiltering> <requestLimits maxAllowedContentLength=”2000000000″ /> </requestFiltering></security>
With the above maxAllowedContentLength, users can upload files that are 2,000,000,000 bytes (2 GB approx) in size. This setting will work right away without restart IIS services.
Alternatively, if the above methods do not work, you can fix the same issue by running "appcmd" command:
C:\Windows\System32\inetsrv\appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:100000000
%windir%\system32\inetsrv\appcmd set config "Default Web Site/<your app>" -section:requestFiltering -requestLimits.maxAllowedContentLength:10000000
In addition to the installation instructions provided, you can find detailed information regarding specific installation instructions in the following documents:
is requesting access to a wiki that you have locked: https://my.axerosolutions.com/spaces/5/communifire-documentation/wiki/view/329/on-premise-installation