Sitecore provides the ability to host multiple sites in a single Sitecore install. Each one of these hosted sites can be serviced by one or more communities with special configuration.
This documentation assumes the implementer has already installed multiple Sitecore sites and understands the configuration of a multi-site installation. If this is not the case, please refer to the documentation for this on the Sitecore Developer Network.
This is how you define configuration options per site while still sharing global options that do not need to be specific - like the location of certain handlers.
<site name="mysecondsite" id="4dfc56c9d13f4103a2661ac3aae05070" />
Once created, mysecondsite will work with Zimbra Connect for Sitecore using exactly the same settings as the website site.
The installation documentation covers the <sites /> node of the TelligentEvolution.config file in your Sitecore App_Config/Include folder. This node contains several attributes which serve as the defaults for Zimbra Connect globally. This is why, when you create the site above, it uses the same settings.
A site can override a setting simply by adding the same attribute with a new value to the its <site /> node. For example, the node below inherits all the configuration values except evolutionRootUrl:
If you are going to use different communities, you need to follow the Zimbra Community installation instructions for each community. Then, at a minimum, you need to override the evolutionRootUrl, oauthClientId, and oauthSecret in the Sitecore configuration for the site. While it's not required, you should also use a unique cookieName for ease of identification:
Powered by Zimbra