The distributed model is typical of web-based applications whose components are distributed across the Web tier, Application tier, and Data tier, and require a secure zone between its web servers and application servers. The other reasons for deploying RiskMinder in a distributed model are as follows:
In a distributed-system deployment, RiskMinder components are installed on different servers. This strategy helps improve security and performance, and also enables multiple applications to use the risk-evaluation functionality.
This deployment model is typically used for production deployments or for staging environments.
The most common deployment is to install RiskMinder Server on one system and one or more web applications on other systems. Because the deployment covers more than one system, an architecture diagram is included for showing which systems must be able to communicate with each other.
To perform a distributed-system deployment you select the Custom installation option (See "Installing on the First System" for more information) option in the RiskMinder installer.
The Component Diagrams for high-availability deployment are discussed in this section.
|
Copyright © 2013 CA.
All rights reserved.
|
|