Table of Contents

Search

  1. Preface
  2. Introduction to High Availability
  3. Set Up the High Availability Environment
  4. Set Up a High Availability Cluster on Windows
  5. Steps to Setting Up a High Availability Cluster in Linux
  6. Optional High Availability Configuration
  7. Troubleshooting High Availability
  8. High Availability Log Messages
  9. Port Number Reference
  10. Glossary

High Availability Installation Guide

High Availability Installation Guide

Operation Console Cluster Components

Operation Console Cluster Components

The Operation Console cluster handles browser requests to and from Operation Console users. The cluster uses a load balancer to distribute the requests between multiple Tomcat instances.
The Operation Console cluster typically consists of the following components:
  • Browser clients.
    B2B Data Exchange
    users log in to the browsers and perform actions in the Operation Console.
  • Load balancer. Receives requests from each Operation Console browser and forwards the requests to the available Tomcat server instance.
  • Tomcat Operation Console server. Receives and processes forwarded requests from the load balancer.
The following figure shows an example of the Operation Console cluster configuration:
Operation Console Cluster, browser 1, browser 2, browser 3, browser request flows to load balancer, forwarded request flows to tomcat A, tomcat B
This cluster consists of three browser clients, one load balancer, and two Tomcat instances that run the Operation Console and the Dashboard. The communication lines between the components represent actions that users perform in the Operation Console that the load balancer distributes between the Tomcat instances. Synchronize the clocks of all machines in the cluster to within 30 seconds of each other to ensure proper handling of browser requests.
The Dashboard is available if you installed the Dashboard and Reports component.

0 COMMENTS

We’d like to hear from you!