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. Appendix A: Troubleshooting High Availability
  8. Appendix B: High Availability Log Messages
  9. Appendix C: Port Number Reference
  10. Appendix D: Glossary

High Availability Installation Guide

High Availability Installation Guide

High Availability Prerequisites

High Availability Prerequisites

Before you set up the high availability environment, verify that your system meets the following prerequisites:
  • It is recommended that the
    B2B Data Exchange
    repository is on a high availability database, such as Oracle Real Application Clusters.
  • The high availability environment includes a clustered file system, such as Global File System (GFS) or Veritas Cluster File System (VxCFS ).
  • The cluster consists of two active
    B2B Data Exchange
    server nodes.
  • The PowerCenter real-time workflows are active and running.
  • A load balancer is installed, such as the F5 Load Traffic Manager or the Apache HTTP Server. For the F5 Load Traffic Manager, we recommend creating sticky session profiles with cookie persistence or source address affinity persistence.
  • The clocks on all
    B2B Data Exchange
    nodes are synchronized to within 30 seconds of each other. Use the Network Time Protocol (NTP) to synchronize the clocks.
  • Both cluster nodes are installed in the same physical location. Geographically distributed nodes are not supported.

0 COMMENTS

We’d like to hear from you!