This chapter describes the software, hardware, and operating system requirements for installing Oracle Communications Messaging Server Cassandra message store hosts. See Messaging Server Installation and Configuration Guide for the software, hardware, and operating system requirements for Messaging Server front-end and message access tier hosts.
This section describes the software requirements for installing Cassandra message store.
Table 4-1 lists operating systems that support Cassandra message store. We recommend that you run the latest software update with the latest recommended patch set.
Table 4-2 lists software required for installing and running Cassandra message store. See Messaging Server Installation and Configuration Guide for other requirements related to Messaging Server itself.
Table 4-2 Software Requirements
| Product | Version | Notes |
|---|---|---|
|
Oracle Java SE Runtime Environment 8 (JRE) or OpenJDK 8 |
1.8.0_40 minimum |
Required on message access tier hosts if they also run the Indexed Search Convertor (ISC). If you are using SSL and need to use the Java keytool utility, you must install Java SE Development Kit (JDK). |
|
Python |
2.7.x |
Required to install Cassandra hosts. |
|
Apache Cassandra |
3.11 |
You can download it from Cassandra website. |
Cassandra node storage requirement is:
Message data center nodes: 5 TB when using SSD (utilization should be less than 70 percent)
Additionally, see the table on hardware requirements for installing Cassandra in the Cassandra documentation.
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.
Cassandra nodes that are configured with the ms_msg keyspace require the most disk capacity to store the message content. Cassandra nodes configured with the ms_cache keyspace collectively should have enough disk capacity for 14 days of converted data stored in the conversion cache.
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.Configure Network Time Protocol (NTP) to ensure that time is synchronized across your deployment.
Cassandra nodes must synchronize their clocks between all hosts accessing Cassandra. All the Cassandra hosts and all the IMAP/LMTP-server tier hosts must have fully synchronized clocks or the deployment becomes unsupportable (both Cassandra-level errors and application errors related to IMAP QRESYNC and CONDSTORE [RFC 7162] will result).
This section describes the information needed before installing and configuring Cassandra message store.
You need the IP addresses of the Cassandra nodes that act as cassconnectpoints when installing and configuring the message access tier nodes.
Table 4-3 shows the Messaging Server options you use to configure racks and data centers when installing and configuring message access tier hosts.