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.2
  • 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 10. Configure the Message Broker for B2B Data Exchange High Availability

Step 10. Configure the Message Broker for B2B Data Exchange High Availability

Configure the
B2B Data Exchange
 JMS Broker on both of the cluster nodes.
  1. On both of the cluster nodes, open the JMS Broker configuration file from the following location:
    <
    DX
    InstallationDir>\DataExchange\message-broker\conf\activemq.xml
  2. In the
    <broker>
     element, in the
    dataDirectory
     attribute, enter the name of a shared directory. For example: 
    <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="/users/infa/node1" useJmx="true">
    Enter a different directory on each cluster node.
  3. In the
    <broker>
     element, add the following element: 
    <plugins>
 <redeliveryPlugin fallbackToDeadLetter="true" sendToDlqIfMaxRetriesExceeded="true">
<redeliveryPolicyMap>
<redeliveryPolicyMap>
<redeliveryPolicyEntries>
<!-- a destination specific policy -->
<redeliveryPolicy queue="SpecialQueue" maximumRedeliveries="4" redeliveryDelay="10000"/>
</redeliveryPolicyEntries>
<!-- the fallback policy for all other destinations -->
<defaultEntry>
<redeliveryPolicy maximumRedeliveries="10" initialRedeliveryDelay="1000" redeliveryDelay="1000"/>
</defaultEntry>
</redeliveryPolicyMap>
</redeliveryPolicyMap>
</redeliveryPlugin>
</plugins>
  4. In the
    <kahaDB>
     element, in the
    directory
     attribute, enter the name of a shared storage directory. For example: 
    <kahaDB directory="/users/infa/sharedFolder"
                checksumJournalFiles="true"
                checkForCorruptJournalFiles="true" />
    Enter the same directory for both cluster nodes.
  5. In the
    <transportConnector>
     element, in the
    uri
     attribute, enter the IP address of the standard message transfer connector. Enter the same port number that you entered in the
    dx.endpoint.jms.provider.url
     system property, in "Step 4: Configure B2B Data Exchange Properties for High Availability". For example: 
    <transportConnector name="openwire" uri="nio://0.0.0.0:18616?useQueueForAccept=false"/>
    Enter the same IP address and port number for both cluster nodes.
  6. Save the file on both cluster nodes.
0 COMMENTS
We’d like to hear from you!