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

Configure JMS Messages Data Directories

Configure JMS Messages Data Directories

Define a shared and reliable location for the cluster to use when sending and receiving JMS messages. The data directory locations may differ depending on the cluster component that processes the JMS messages and the operating system that you use.
If you change the default directory, add the dx.jms.dataDirectory property to the relevant configuration file and set the value to the new directory, such as:
dx.jms.dataDirectory=C:/data_directory
The configuration files for each cluster component that processes JMS messages are located in the following folders:
  • B2B Data Exchange JMS Broker:
    <Data Exchange Installation Directory>\DataExchange\message-broker\conf\activemq.xml
  • Data Exchange server:
    <Data Exchange Installation Directory>\DataExchange\conf\dx-configuration.properties
  • Operation Console:
    <Data Exchange Installation Directory>\DataExchange\tomcat\shared\classes\dx-configuration.properties
The following table describes the default JMS message storage directories for all parts of the B2B Data Exchange JMS Broker component:
Part
Default Directory Location
Windows service
<Data Exchange Installation Directory>\DataExchange\message-broker\data\
Windows command line script
<Data Exchange Installation Directory>\DataExchange\message-broker\data\
UNIX command line script
<Data Exchange Installation Directory>/DataExchange/message-broker/data/
The following table describes the default JMS message storage directories for all parts of the Data Exchange server component:
Part
Default Directory Location
Windows service
<Data Exchange Installation Directory>\DataExchange\activemq-data\
Windows command line script
<Data Exchange Installation Directory>\DataExchange\activemq-data\
UNIX command line script
<Data Exchange Installation Directory>/DataExchange/activemq-data/
The following table describes the default JMS message storage directories for all parts of the Operation Console component:
Part
Default Directory Location
Windows service
<WindowsServicesWorkingDirectory>\activemq-data
The typical working services working directory is:
C:\Windows\System32\
Windows command line script
<Data Exchange Installation Directory>\DataExchange\tomcat\bin\activemq-data\
UNIX command line script
<Data Exchange Installation Directory>/tomcat/bin/activemq-data/
0 COMMENTS
We’d like to hear from you!