It is important to know Rich Media Server performance does not only depends on Rich Media Server itself but it also depends on operating system, java virtual machine, application server and database, as well as connections pools between every architecture tier.
Rich Media Server reliability, availability and scalability rely on platform hardware and software ability to provide required performance level.
Streamezzo is not in charge of providing information about how to set up every platform component for improving performance.
Integrators are supposed to provide required skills for setting up platform hardware and software.
In a production environment, Rich Media Server is supposed to be tuned.
Main rule consists in storing cached data into memory cache instead of database cache.
Rich Media Server comes with built-in features for relying on Ehcache framework for storing data into memory.
RMS Administrative Console general settings page is supposed to display the following:
Here is an overview of a typical Rich Media Server production environment:
|
| Figure: Rich Media Server platform overview |
A single Rich Media Server Administrative Console is required for managing a cluster. Rich Media Server configuration data is stored into the Rich Media Server database, which can be shared among several Rich Media Server instances running on distinct servers. For security purpose, it is strongly advised to deploy Rich Media Server Administrative Console into back end tier and remove it from Rich Media Server instances running into front end tier. You can refer to Rich Media Server Clustering Guide for more information about deploying several Rich Media Server instances within highly available JEE multi-tier platforms.