Before installing a new community, ensure that you have met all the hardware and software.
This installation procedure has been divided by installation area so that multiple administrators can install different aspects of a Zimbra Community site.
This procedure assumes you already have IIS installed, and have configured the Database and Search servers.
Create a web directory folder and copy the files there:
For further details on optimizing the performance of your web server, see Web Server configuration check-list.
You can't configure the connectionstrings file until after you create the database.
For assistance with connection strings, you can refer to http://connectionstrings.com. (Zimbra has no affiliation with the site.)
<add name="SiteSqlServer" connectionString="server=SERVERNAME;database=DATABASENAME;Trusted_Connection=yes;" />
<add name="SiteSqlServer" connectionString="server=SERVERNAME;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=no;" />
<add name="SiteSqlServer" connectionString="server=(local)\SQLExpress;database=DATABASENAME;Trusted_Connection=yes;" /><add name="SiteSqlServer" connectionString="server=(local)\SQLExpress;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=yes;" />
This should only be a quick test - any functionality that requires search will not work yet.
Important: Solr should never be accessible to the public. Ensure that neither the Tomcat home page nor the Solr home page is publicly accessible. If this endpoint is accessible, work with your IT department or read Securing Solr on Tomcat for more details on blocking this endpoint from the public.
<Override xpath="/CommunityServer/Search/Solr" mode="change" name="host" value="http://yourserver:XXXX/PathToSolr/content" />
The Solr path URL is case-sensitive.
For further details on optimizing the performance of your database server, see database configuration and database maintenance.
Create a new database in SQL Server. For information about supported versions, please see Supported software versions for servers, applications, and browsers.
Populate the database by executing the cs_CreateFullDatabase.sql script from the \SqlScripts\ folder of the install package.
Create the community by executing the cs_SystemCreateCommunity 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/zimbra_evolution' , @ApplicationName = N'zimbra_evolution' , @AdminEmail = Nfirstname.lastname@example.org' , @AdminUserName = N'admin' , @AdminPassword = N'[PUT YOUR PASSWORD HERE]' , @PasswordFormat = 0
, @CreateSamples = 0
where you specify the appropriate values for each parameter:
Once you have created your community, we recommend you create a new administrator account and delete the one you created when setting up your community. This is to ensure that your administrator account's password is encrypted in the database. (While it is possible to encrypt the administrator account's password when you create the community, you need to provide the hashed password for the @AdminPasswordparameter, which starts getting more complicated than it's worth, given the easy workaround.)
For this information, see Database maintenance.
Zimbra Evolution relies on search for some core functionality. It must be installed and set up properly for the site to fully function. Follow these instructions to Install and configure search.
Please refer to Install the Zimbra Job Service for installation instructions.
The socket message bus server enables real-time features to scale across web farms, and must be installed and enabled in multiple-instance environments. It is not required if only running Zimbra Community on a single web instance.
Alternatively, a custom or third party message bus server can fill this role as well, as long as a connector plugin is written and deployed for it.
The Socket Message Bus server should have a single installation with multiple web app instances connecting to it. By default, it communicates over port 9623. It should only be made available the web apps.
Set up a Caching Server
Please refer to the Zimbra Community Troubleshooting Guide.
You may need to navigate to the Zimbra license file from obtained from Support in order to add users, groups, and applications.
Powered by Zimbra