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

B2B Data Exchange Server Configuration Properties

B2B Data Exchange
Server Configuration Properties

You configure JMS discovery for each
B2B Data Exchange
server node in the cluster based on the mode that you want to use.
To configure JMS discovery, you modify configuration properties in all copies of the dx-configuration.properties file. The Operation Console file is typically located in the following directory:
<
DX
InstallationDir>\conf\
. The
B2B Data Exchange
server file is located in the following directory:
<
DX
InstallationDir>\
DataExchange
\tomcat\shared\classes
.
The following table describes the JMS discovery configuration properties:
Property
Description
dx.console.jms.unicastAddress
IP address and port number of the Operation Console to use in unicast mode.
Default value:
0.0.0.0:18050
For single-machine clusters, each
B2B Data Exchange
server instance must have a different port number.
dx.jms.multicastAddress
IP address and port number of the Operation Console to use in multicast mode.
Default value:
224.252.253.254:18000
For single-machine clusters, each
B2B Data Exchange
server instance must have a different port number.
dx.cluster.name
Logical name of the
B2B Data Exchange
server cluster. Must be identical for all of the nodes in the cluster.

0 COMMENTS

We’d like to hear from you!