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
  • Multidomain MDM 10.3 HotFix 3
  • All Products

Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Pre-Installation Tasks
  4. Hub Store Installation
  5. Hub Server Installation
  6. Hub Server Post-Installation Tasks
  7. Process Server Installation
  8. Process Server Post-Installation Tasks
  9. ActiveVOS Post-Installation Tasks for the Application Server
  10. ActiveVOS Post-Installation Tasks for the Business Entity Adapter
  11. Resource Kit Installation
  12. Resource Kit Post-Installation Tasks
  13. Troubleshooting the MDM Hub
  14. Uninstallation

Installation Guide for IBM DB2 with Red Hat JBoss

Installation Guide for IBM DB2 with Red Hat JBoss

Back Next

Configuring the Hub Server for a JBoss Multi-node or Cluster Environment

Configuring the Hub Server for a JBoss Multi-node or Cluster Environment

If you installed the Hub Server in a JBoss multi-node or a cluster environment, configure the Hub Server for the JBoss environment. To configure the Hub Server for the JBoss environment, configure the JBoss environment properties in the
cmxserver.properties
 file.
For example, if a JBoss cluster or the multi-node environment has two nodes, which run on host1 and host2, configure the JBoss environment properties on both the nodes.
  1. On all nodes in the environment, open the
    cmxserver.properties
     file in the following directory:
    <
    MDM Hub installation directory
    >/hub/server/resources
  2. Configure the following JBoss environment properties:
    Property
    Description
    jboss.cluster
    Specifies whether EJB servers have multiple nodes or are clustered for the Hub Server. Add the
    jboss.cluster
     property, and set it to
    true
    .
    cmx.appserver.hostname
    Specifies machine names of the JBoss multi-node or the cluster environment. The machine names must be in the following format:
    <
    host name
    >.<
    domain
    >.com
    For example, if the cluster or the multi-node environment has two nodes that run on host1 and host2 and use RMI ports 4447 and 4448, set
    cmx.appserver.hostname=host1.<
    domain
    >.com,host2.<
    domain
    >.com
    cmx.appserver.rmi.port
    Specifies remote port numbers.
    For example, if the cluster or the multi-node environment has two nodes, which run on host1 and host2 and use RMI ports 4447 and 4448, set
    cmx.appserver.rmi.port=4447,4448
    Separate the port numbers by a comma with no space between them. Ensure that the order of the port numbers corresponds to the order of the host names.
0 COMMENTS
We’d like to hear from you!