Redcell Deployment Architecture

Redcell supports three primary deployment models:

Single-Server -- The full application is installed on one server.

Distributed-Server -- One or more servers are distributed.

Clustered/HA -- multiple servers of each type may be used for performance gains or to achieve High Availability.

The Redcell platform software architecture consists of the following principal run-time software components:

Web Server -- Eliminates the need for a separate Java client interface. Deployments that have more that one web server or application server also require a load balancer.

Application Server -- The system's central processing unit. It executes application business logic. You can deploy it in both fault tolerant (Master/Slave) and cluster configurations to limit downtime and optimize performance.

Upgrading application server first, if you are using the embedded database, also upgrades the database, if necessary. It’s often easiest to install application server first simply because this upgrade impacts any other application servers too, if they are clustered.

Database Server -- Like the Application Server, you can deploy the Database Server in a fault tolerant configuration to eliminate data loss during a system failure and to ensure data integrity. This configuration typically uses Mysql replication or Oracle RAC. You can cluster the Oracle database servers. See Installing Oracle. References to database servers below apply to all supported databases.

Mediation Server -- Mediation Server manages the communication between the Redcell Synergy and the network elements. Like the application and database servers, you can deploy mediation servers in a fault tolerant master/slave configuration to maintain constant communication with the network elements. You can make mediation servers highly available. See Mediation Clustering.

If Mediation Servers or clients are outside a firewall from the Application Server, you must disable multicast connections to Application Servers. See Disabling Multicast.

Load Balancer (Proxy) -- Deployments where many users access the system concurrently may require a Load Balancer, also known as a Proxy, to manage traffic to multiple Web Servers. If one web server is overloaded or un-responsive, the Load Balancer directs users to a responsive Web server. Single-server installations do not require a Load Balancer.

All deployments with multiple application servers require an additional load balancer for application servers too. This ensures that active web servers always direct traffic to an available application server in the cluster. If the current application server is unresponsive, the load balancer re-directs the web server to another application server.

With the proper configuration the same load balancer can serve both web server and application server. See Synergy + HA Load Balancer or Configuring Load Balancer for more.