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.5.0
  • 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

Configuring Unicast JMS Discovery

Configuring Unicast JMS Discovery

Modify properties in different cluster components to enable unicast JMS discovery in the high availability cluster.
Make sure you configure the same JMS discovery mode in every file. You cannot configure some properties for unicast mode and other properties for multicast mode.
  1. In all copies of the
    B2B Data Exchange
     server configuration files, add the following properties and replace the syntax example with the actual values:
    • dx.AMQ.discovery=b2bDxAMQBrokerStatic
    • dx.AMQ.static.discovery.address=static:(tcp://<host1Name>:<OperationConsoleJMSPort>,tcp://<host1Name>:<
      DX
      ServerJMSPort>, tcp://<host2Name>:<OperationConsoleJMSPort>,<host2Name>:<
      DX
      ServerJMSPort>)
    For example:
    dx.AMQ.static.discovery.address=static:(tcp://host1:18100,tcp://host1:18050, tcp://host2:18100,tcp://host2:18050)
  2. Add comment indicators to the following properties that are relevant only for multicast mode:
    • dx.cluster.name
    • dx.jms.multicastAddress
  3. In all copies of the activemq.xml file, remove the comment indicator from the static networkConnector name property, and update the host names and ports.
    There is one
    activemq.xml
     file at each
    B2B Data Exchange
     node. The file is located at the following path:
    <
    DX
    InstallationDir>\DataExchange\message-broker\conf\
  4. Modify the value of the dataDirectory property
    and the value of the kahaDB directory property
    to point to a shared storage directory.
  5. In the
    B2B Data Exchange
     system property list, modify the value of the dx.endpoint.jms.provider.url property to use failover transport with the following syntax: 
    failover://(nio://host1:18616,nio://host2:18616)?jms.prefetchPolicy.queuePrefetch=1
  6. In the PowerCenter Workflow Manager, select
    Connections
    Application
     and modify the JNDI provider URL of the JMS connection factory, for example: 
     failover:(nio://10.36.8.26:18616,tcp://10.36.8.38:18616)
?jms.prefetchPolicy.queuePrefetch=1
0 COMMENTS
We’d like to hear from you!