FusionReactor 4 encompasses several technologies designed to ease the burden of J2EE (including ColdFusion) support organizations – two of which are Enterprise Monitoring and Crash Protection.
Crash Protection is, of course, one of the important features of FusionReactor, and has been present since the initial release. FR4 builds on this technology and brings advances in Restrictions (which requests will be subject to Crash Protection) and we have also extensively reviewed the mechanisms FusionReactor uses to manage and control requests. Server downtime is often measured in dollars, not minutes, and Crash Protection continues to be a focus of the FusionReactor team.
Enterprise Monitoring (available to customers with enterprise licenses) gives you the ability to visualize the state of a machine cluster, together with behind-the-scenes uptime monitoring, and the ability to send mail when a machine becomes unavailable. Easy-to-read instrumentation including color-coding, realtime graphs and bars, together with advanced grouping, server-offlining and user-definable warning and critical thresholds make our Enterprise Dashboard an essential component for hosting providers, or customers with a cluster of J2EE (e.g. ColdFusion) installations.
The Enterprise Dashboard is fully explained in its own section, so we won't be covering it here, except where necessary to illustrate how a particular issue is visualized.
Scenarios and Scope
This documentation will cover the usage of FusionReactor to ensure the availability of your systems. We'll cover Crash Protection and Enterprise Monitoring in some detail. We'll show you how to use FusionReactor to cross-monitor a cluster of machines, such as is typically found within companies with fail over solutions, or in hosting providers running large farms of machines.
We'll illustrate in detail, using worked examples, how FusionReactor's sophisticated Crash Protection works to keep your system up and alive, even in the face of an onslaught of requests, bad queries, pages that take too long and memory which is approaching upper margins.
Although every installation of FusionReactor is different – and we're constantly amazed at the diverse and interesting environments FusionReactor is deployed within – we'll also show you how you might tune Crash Protection to optimize your production environments.
Finally, we hope you are happy with FusionReactor. We're convinced it will provide a significant return on your investment, maybe in some cases even paying for itself by preventing one outage. Over multiple version releases we have made significant advances in enterprise monitoring, protection and visualization, but a lot of it would not have been possible without feedback from our customers. We're always grateful for comments on our products; if you have any criticisms or ideas, please send them to: firstname.lastname@example.org
- Design Goals
- Crash Protection Implementation
- The Crash Protection Restrictions Engine
- Test Pages
- Exercising Timeout Protection
- Exercising Memory Protection
- Exercising Request Quantity Protection
- Using the Redirect Method
- Rule Basics
- Examples of Restrictions