Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • B2B Data Exchange 10.2.1
  • All Products

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

Back Next

Step 5. Configure B2B Data Exchange Properties for High Availability

Step 5. Configure
B2B Data Exchange
 Properties for High Availability

Configure
B2B Data Exchange
 properties on both of the cluster nodes.
  1. On both of the cluster nodes, open the
    B2B Data Exchange
     properties configuration file from the following location:
    <
    DX
    InstallationDir>/conf/dx-configuration.properties
  2. Add a comment indicator to the
    dx.jms.multicastAddress
     property.
  3. Remove the comment indicator from the
    dx.AMQ.discovery
     property.
  4. Remove the comment indicator from the
    dx.AMQ.static.discovery.address
     property and replace the syntax example with real values. Each node in the cluster requires two entries.
    For example: 
    dx.AMQ.static.discovery.address=static:(tcp://node1:18100,tcp://node1:18050,tcp://node2:18100,tcp://node2:18050)?jms.prefetchPolicy.queuePrefetch=1
  5. In the
    dx.cluster.name
     property, provide the same name for every cluster node.
  6. Save the file on both cluster nodes.
  7. On both of the cluster nodes, perform steps 2 to 6 in the the following file: 
    <
    DX
    InstallationDir>/
    DataExchange
    /tomcat/shared/classes/dx-configuration.properties
  8. Ensure that you have load balanced the
    B2B Data Exchange
     servers as relevant to the type of load balancer. Load balance the
    B2B Data Exchange
     URL at port 19553.
  9. In the
    B2B Data Exchange
     Operation Console, from the Navigator, open
    Administration
    System Properties
    .
  10. Change the value of the
    dx.console.url
     property to the load balancer URL, in the following format:
    http://<load_balancer>:<load_balancer_port>/
    dx
    -console
     .
    For example:
    http://host1:80/
    dx
    -console
  11. Change the value of the
    dx.endpoint.jms.provider.url
     property to use failover transport. Each node in the cluster requires one entry.
    For example: 
    failover://(nio://node1:18616,nio://node2:18616)?jms.prefetchPolicy.queuePrefetch=1
0 COMMENTS
We’d like to hear from you!