Skip to content

Latest commit

 

History

History
161 lines (136 loc) · 7.36 KB

packages.adoc

File metadata and controls

161 lines (136 loc) · 7.36 KB
Raw

{product-short} Application Packages

{product-short} architecture includes open-source integrations using industry standard protocols. The third-party software has been tested and configured to work with the {product-short} software.

The following describes the {product-name} application packages that are installed.

  • {product-short} Core: This package includes the libraries, utilities, monitoring tools, and basic configuration files. {product-short} Core is automatically installed on each server.

  • {product-short} LDAP: User authentication is provided through OpenLDAP® software. Each account on the Zimbra server has a unique mailbox ID that is the primary point of reference to identify the account. The OpenLDAP schema has been customized for {product-name}.

    Note
    		 The {product-short} LDAP server must be configured before any other servers.

    You can set up LDAP replication, configuring a master LDAP server and replica LDAP servers.

  • {product-short} Store: This package includes the components for the mailbox server, including Jetty, which is the servlet container the {product-short} software runs within. The {product-short} mailbox server includes the following components:

    • Data store: The data store is a MariaDB© database.

    • Message store: The message store is where all email messages and file attachments reside.

    • Index store: Index and search technology is provided through Lucene. Index files are maintained for each mailbox.

    • Web application services: The Jetty web application server runs web applications (webapps) on any store server. It provides one or more web application services.

  • {product-short} MTA: Postfix is the open source mail transfer agent (MTA) that receives email via SMTP and routes each message to the appropriate {product-short} mailbox server using Local Mail Transfer Protocol (LMTP). The {product-short} MTA also includes anti-virus and anti-spam components.

  • {product-short} Proxy: {product-short} Proxy is a high-performance reverse proxy service for passing IMAP[S]/POP[S]/HTTP[S] client requests to other internal {product-name} services using nginx. This package is normally installed on the MTA server(s) or on its own independent server(s). When the zimbra-proxy package is installed, the proxy feature is enabled by default.

    Note
    		 Installing the {product-short} Proxy is required as of {product-abbrev} 8.7.
Note
 By default {product-short} Proxy is configured to perform strict server name enforcement of the HTTP 'Host' header sent by clients for new installs. Strict server name enforcement may be disabled during the post-install configuration process in the {product-short} Proxy configuration section or using the zimbraReverseProxyStrictServerNameEnabled configuration option. Please see the {product-short} Proxy section of the administration guide for more details.

  • {product-short} Memcached: This package is automatically selected when the {product-short}-Proxy package is installed and provides access to Memcached.

    Note
    		 At least one server must run zimbra-memcached when the {product-short} Proxy service is in use.

    You can use a single memcached server with one or more {product-short} proxies.

  • {product-short} SNMP: Installing this package is optional.

    Note
    		 If you choose to install {product-short}-SNMP for monitoring, this package should be installed on every {product-short} server.

  • {product-short} Logger: Installing this package is optional. It is installed on one mailbox server. It provides tools for syslog aggregation and reporting.

    Note

    • If you do not install {product-short} Logger, the server statistics section of the administration console will not display.

    • The {product-short} Logger package must be installed at the same time as the {product-short} Store package.

  • {product-short} Spell: This package is optional. It provides the open source spell checker Aspell used by the {product-short} Web Client.

  • {product-short} Apache: This package is installed automatically when {product-short} Spell is installed.

  • {product-short} Convertd: This package should be installed on at least one {product-short}-Store server. Only one {product-short}-Convertd package needs to be present in the {product-name} environment. The default is to install one {product-short}-Convertd on each {product-short}-Store server.

  • {product-short} Connect: Installing this package is optional. This package should be installed on at least one {product-short}-Store server. {product-short} Connect includes a server extension with all the necessary modules to run an embedded XMPP Server, and an End-User Zimlet which connects to the server extension and offer to the users a rich point-to-point text-chat conversations. {product-short} Connect is marked as GA and supported starting {product-name} 8.8.

    Note
    		 The {product-short} Connect package must be selected and installed on every {product-short}-Store.

  • {product-short} Drive: Installing this package is optional.This package should be installed on at least one {product-short}-Store server. {product-short} Drive is marked as GA and supported starting {product-name} 8.8.

{product-short} Drive includes a server extension with all the necessary modules to connect and authenticate {product-short} users against a ownCloud or NextCloud Server, and an End-User Zimlet which allow users to perform actions to the their docu- ments stored on ownCloud or Nextcloud.

Note
 The {product-short} Drive package must be selected and installed on every {product-short}-Store.
Warning
 Zimbra Drive only provides connectivity to a ownCloud or NextCloud Server. It is the Customer’s responsibility to maintain, backup, and protect the data stored on ownCloud or NextCloud Servers.

The {product-short} server configuration is menu driven. The installation menu shows you the default configuration values. The menu displays the logical host name and email domain name [mailhost.example.com] as configured on the computer. You can change any of the values. For single server installs, you must define the administrator’s password, which you use to log on to the administration console, and you specify the location of the {product-short} license xml file.