Preface
Introduction to High Availability
Set Up the High Availability Environment
Configure JMS Discovery
Configure RMI Connections
- RMI Connections Overview
- Configuring RMI Connections
Configure the Operation Console
- Configuring a Proxy Server for the Operation Console
- Configuring Tomcat for Single-Machine Clusters
Configure an HTTP Load Balancer
Configure the Dashboard and Reports
- Dashboard and Reports Configuration Overview
- Configuring the Dashboard and Reports to Use the Load Balancer
Troubleshooting High Availability
- Troubleshooting High Availability
High Availability Log Messages
- High Availability Log Messages
Port Number Reference
- Port Number Reference
Glossary
- Glossary of Terms
  - active node
  - active/active
  - active/passive
  - AJP
  - browser
  - client
  - failover
  - grid
  - load balancer
  - recovery
  - resilience
  - sticky session
  - Tomcat instance

High Availability Guide

10.4.0
- 10.5
- 10.4.1

Back Next

High Availability Overview

When you use

Data Integration Hub

to process

publications and subscriptions

on a large scale, you need to provide continuous service even if one component fails. You set up a high availability environment with failover mechanisms that can handle a failed server or service.

You can configure a high availability cluster with multiple machines in a network or with a single multi-processor machine. A high availability cluster includes multiple installations of typical

Data Integration Hub

components that communicate with each other in the background while providing a single point of operation for users.

Rename Saved Search

Table of Contents

High Availability Guide

High Availability Guide

High Availability Overview

High Availability Overview