Consolidation — Rhino 2.2 consolidates bug fixes from all Rhino 2.1 patch releases.
Rhino 2.2 now logs all management operations to two log files in the working directory of each Rhino node: a plain text CSV file; and an encrypted CSV file. This provides a tamper-proof record of all management operations performed on a node.
In addition, all audit log records include (but are not limited to):
An operation code
Parameters of the operation
Username of the administrative user requesting the operation
IP address of the client computer requesting the operation
Rhino 2.2 includes an SNMP agent, for interoperability with external SNMP-aware management clients. The Rhino SNMP agent provides a read-only view of Rhino's statistics (through SNMP polling), and supports sending SNMP notifications for platform events to an external monitoring system. This means that both Fault Management and Performance Management statistics can now be output. Rhino 2.2 has been tested with OpenNMS version 1.8.x
The Rhino Element Manager (REM) is a brand new OAM function for Rhino, which replaces the previous web-console.
The Element Manager is used for configuration management, and provides:
Connection with Rhino 2.0, Rhino 2.1 and Rhino 2.2 releases
Role based access to EM functions
"Umbrella view" - heads up display of several different Rhino clusters
Includes Single-Sign-On support (HTTP authentication and HTTPS authentication)
The Rhino Element Manager allows visual management of many Rhino subsystems including (but not limited to) the following
Platform and Deployable Unit lifecycle
RAs, RA entities
Container configuration (Object pools)
Rhino 2.2 has been enhanced to deal with the higher call rates that customers are now experiencing. Improvements to the Savanna changes have increased throughput when using call state/session replication. The Rhino 2.2 Benchmarks show a more linear scalability curve for both number of cores and number of nodes when compared with Rhino 2.1
Improved latency during replication Our benchmarking demonstrates that call setup times can be reduced by as much as 36% using Rhino 2.2
Rhino 2.2 builds with Java 6. It has been tested with Java 6 running in 64-bit mode to deal with the higher throughput our customers are demanding. OpenCloud now supports this JVM on Solaris 10 and RHEL 5.5 Linux Operating Systems. This means that Rhino 2.2 is Java 6 (SE) only and no longer supports Java 5 (SE)
Oracle 11g can now be used in place of PostgreSQL as the backing database, for customers who wish to use Oracle.