Table of Contents

Search

  1. Preface
  2. Introduction to RulePoint
  3. Managing Your Account
  4. Using RulePoint User Interface
  5. User Management
  6. Topology Management
  7. Managing Hosts and Nodes
  8. Managing Application Services
  9. Managing System Services
  10. High Availability
  11. Managing Deployment
  12. Dashboard
  13. Object Import and Export
  14. Markers
  15. Log Management
  16. Licenses
  17. Error Codes
  18. Glossary

Administrator Guide

Administrator Guide

Best Practices for Achieving High Availability

Best Practices for Achieving High Availability

To optimize RulePoint availability, ensure that you adopt the best high-availability strategy to configure all the run-time components.
Use the following rules and guidelines when you set up high availability:
  • Replicate the application services across multiple nodes. Running the processes on multiple nodes balances the run-time services workload, and processes faster.
  • Run the primary instance and the backup instance of the application services on different nodes to ensure that even if one node goes down, another node continues to provide the service. Running the nodes on different host machines ensures that even if one host goes down, the nodes on other hosts will take over the activity.
  • Run the active grid manager instance and its backup instance on different hosts, to ensure that even if one host goes down, the grid manager process is still available.
  • Run the UM store on different hosts to ensure its high availability.
  • Ensure that the database and network are continually available to help in the overall high availability of the system.

0 COMMENTS

We’d like to hear from you!