7 Messaging Server System Requirements
This chapter describes the software, hardware, and operating system requirements for installing Oracle Communications Messaging Server and Elasticsearch.
For information about Cassandra message store requirements, see Messaging Server Installation and Configuration Guide for Cassandra Message Store.
Software Requirements
This section describes the software requirements for installing Messaging Server.
Supported Operating Systems
Table 7-1 lists operating systems that support Messaging Server. For all operating systems, we recommend that you run the latest software update with the latest recommended patch set.
Table 7-1 Supported Operating Systems
| Operating System | CPU | Required Patches |
|---|---|---|
|
Oracle Solaris 11.4 |
SPARC, x64 |
See the Oracle Solaris documentation for patch information. |
|
Oracle Linux 7.2 Red Hat Linux 7.2 |
x64 |
See the Oracle Linux and Red Hat Enterprise Linux documentation for patch information. |
Supported High Availability Software
Table 7-2 lists high availability software support for Messaging Server.
Table 7-2 Supported High Availability Software
| Product | Operating System | Version |
|---|---|---|
|
Oracle Clusterware |
Solaris SPARC |
18.3 |
|
Oracle Clusterware |
Solaris x86 |
18.3 |
|
Oracle Clusterware |
Red Hat Enterprise Linux |
18.3 |
|
Oracle Clusterware |
Oracle Linux |
18.3 |
Required Software
Table 7-3 lists software required for installing and running Messaging Server.
Table 7-3 Software Requirements
| Product | Version | Notes |
|---|---|---|
|
Oracle Directory Server Enterprise Edition |
Oracle Directory Server Enterprise Edition 6.x, 7, 11.x |
For a fresh installation, use the latest version of Directory Server 11gR1. |
|
Directory Server Setup Script (comm_dssetup.pl) |
6.4.0.28 and higher |
To prepare the LDAP directory for Messaging Server. |
File System Recommendations
This section describes the file system requirements for installing Messaging Server.
Table 7-4 shows the file systems that are recommended for Messaging Server message stores.
Table 7-4 Messaging Server Clients
| File System | Comments |
|---|---|
|
LUFS (Logging UFS) |
No comments. |
|
VxFS (Veritas File System) |
Veritas File System provides good system performance if configured properly. If you use VxVM, the Veritas Volume Manager, you need to watch carefully that the volumes and the log file for the volumes are set to be regularly striped. |
|
HAStoragePlus File System for Oracle Solaris Cluster installations |
The HAStoragePlus File System provides better performance than the default Oracle Solaris Cluster Global File System. |
|
NFS (Network File System) |
We support use of NFS as storage that is accessed by a single machine at a time. It can also be used to share autoreply and defragmentation histories between MTAs. See Messaging Server System Administrator's Guide for more information and setup details. |
|
ZFS |
See the topic on Messaging Server ZFS support in the Messaging Server System Administrator's Guide for more information. |
Hardware Requirements
This section describes the hardware requirements for installing Messaging Server.
The number and configuration of the systems that you employ for your Messaging Server installation depends on the scale and the type of deployment you have planned.
Note:
The sizing estimates in this section assume proper application configuration and tuning, in a manner consistent with leading practices of Oracle Communications consulting and performance engineering. This information is provided for informational purposes only and is not intended to be, nor shall it be construed as a commitment to deliver Oracle programs or services. This document shall not form the basis for any type of binding representation by Oracle and shall not be construed as containing express or implied warranties of any kind. You understand that information contained in this document will not be a part of any agreement for Oracle programs and services. Business parameters and operating environments vary substantially from customer to customer and as such not all factors, which may impact sizing, have been accounted for in this documentation.
Table 7-5 provides the minimum hardware requirements for Messaging Server.
Table 7-5 Minimum Hardware Requirements
| Component | Requirement |
|---|---|
|
Disk Space |
Approximately 1 GB required for Messaging Server software. You also need adequate space for message store, database configuration directory, and log files, depending upon your site size. |
|
RAM |
1 GB |
Time Synchronization Requirements
Configure Network Time Protocol (NTP) to ensure that time is synchronized across your deployment.
Information Requirements
This section describes the information needed before installing and configuring Messaging Server.
During the Messaging Server installation, you must enter values for configuration items such as host names and port numbers. This section describes the information that you must provide during the installation and initial configuration process.
Messaging Server Information
Table 7-6 lists the Messaging Server information that you provide during initial configuration.
Table 7-6 Messaging Server Information
| Information Type | Default Value | Comments |
|---|---|---|
|
DataRoot |
/var/opt/sun/comms/messaging64 |
No comments. |
|
User name for server processes |
mailsrv |
No comments. |
|
Group name for server processes |
|
If the user name for server processes already exists, then the primary group for that user name is used, and no option is prompted for. |
|
Fully qualified host name of this system |
FQDN of host |
No comments. |
|
Default mail domain name |
Domain of host |
No comments. |
LDAP Information
Table 7-7 lists the LDAP information that you provide during initial configuration.
Table 7-7 LDAP Information
| Information Type | Default Value |
|---|---|
|
Directory Server host name |
Defaults to the loopback interface (where LDAP would live in a single-host evaluation deployment). |
|
User/Group directory manager distinguished name (DN) |
cn=Directory Manager |
|
Directory manager password |
No default value. |
Postmaster, Administrator, and IP Relay Information
Table 7-8 lists the additional information that you provide during initial configuration.
Table 7-8 Notification Information
| Information Type | Default Value |
|---|---|
|
Mail address for postmaster notices |
admin@domain. |
|
Password for server administration |
No default. |
|
Mail relay IP addresses (systems permitted to relay mail without authentication) |
No default, but if nothing is provided, only connections from the host to itself can relay without authentication. |
Directory Server Information
Table 7-9 lists the additional information that you provide during the Directory Server configuration with initial configuration.
Table 7-9 Directory Server Information
| Option | Default Value |
|---|---|
|
Instance Directory |
/var/opt/SUNWdsee/dsins1 |
|
Directory Instance Port |
389 |
|
Directory instance SSL Port |
636 |
|
Directory Manager DN |
cn=Directory Manager |
|
Directory Manager Password |
Directory Manager password provided to Messaging Server initial configuration. |
Front-End / Back-End Compatibility Matrix for Messaging Server Versions
This sections provides a compatibility matrix for front-end and back-end servers for different versions of Messaging Server for the various protocols. Table 7-10 lists the versions of the front-end, the protocol, and compatible back-end versions.
Table 7-10 Front-End / Back-End Compatibility Matrix for Messaging Server Versions
| Front End | Protocol | Back End |
|---|---|---|
|
MS 7/8 MMP * |
IMAP/POP + SASL PLAIN |
Standards Compliant IMAP/POP (including old MS versions) |
|
MS 7/8 MTA |
SMTP Relay |
Standards Compliant SMTP servers |
|
MS 7/8 MTA |
Customized LMTP |
MS 7/8 LMTP server |
|
MS 7/8 mshttpd |
SMTP Submit + SASL PLAIN |
MS 7/8 MTA |
|
MS 7.0.5.31.0/8 mshttpd ** |
IMAP + extensions |
MS 8 IMAP server |
|
MS 7/8 mshttpd |
IMAP + extensions |
MS 7 IMAP server |
|
MS 8.0.1/8.0.2/8.1 |
Cassandra/classic store failover + IMAP, POP, LMTP |
MS 8.0.2/8.1 |
|
MS 8.0.2/8.1 MMP/MTA/MSHTTP *** |
Cassandra store round-robin + IMAP, POP, LMTP |
MS 8.0.2/8.1 IMAP/POP/LMTP server |
* Be sure to configure the MMP's IMAP capability string to be the subset of capabilities offered by all back-ends.
** Older versions of mshttpd have a bug that breaks compatibility with 8.0+ IMAP.
*** See hostselect proxy option in Messaging Server Reference for details.
Software Requirements for Elasticsearch
This section describes the software requirements for installing Elasticsearch version 7.6.1.
For information about Supported Operating Systems to install Elasticsearch, visit the Elasticsearch website at
Required Software
Table 7-11 lists software required for installing Elasticsearch.
Table 7-11 Software Requirements
| Product | Version | Notes |
|---|---|---|
|
Oracle Java SE Runtime Environment 8 (JRE) or OpenJDK 14. |
1.8.0_40 minimum |
Required on message access tier hosts if they also run the Indexed Search Converter (ISC). If you are using SSL and need to use the Java keytool utility, you must install Java SE Development Kit (JDK). |
Modifying Elasticsearch Configuration
To accommodate indexing of messages larger than 100 MB, before starting Elasticsearch service, you must set the http.max_content_length configuration value in the Elasticsearch.yml file according to your requirements.
For more information, see https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html.