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

Install the Process Server on Nodes in the Cluster

Install the
Process Server
 on Nodes in the Cluster

In application server cluster environments, install the
Process Server
 on all nodes of the cluster to which you must deploy the
Process Server
 application. You must complete the installation on one node of a cluster before you proceed to install on another node of a cluster.
For example, a JBoss cluster has two nodes that run in host1 and host2 and use RMI ports 4447 and 4448. You need to install the
Process Server
 on node1 and node2. You must complete the
Process Server
 installation on any one node, such as node2, before you start installation on the other node, node1.
Ensure that the directory structure of the
Process Server
 installation is the same on all the nodes.
  1. Start the JBoss application server on each cluster node.
  2. Navigate to the following directory:
    <
    MDM Hub distribution directory
    >/<
    operating system name
    >/mrmcleanse
  3. Navigate to the following directory:
    <
    MDM Hub distribution directory
    >/<
    operating system name
    >/mrmcleanse
  4. To start the
    Process Server
     installer on a cluster node, run the command for your operating system:
    UNIX
    .
    ./hub_cleanse_install.bin
    Windows
    .
    hub_cleanse_install.exe
    The
    Process Server
     installation wizard starts.
  5. Follow the online instructions. When prompted, enter the installation values that you collected.
  6. Next step
    : After the installation completes, deploy the
    Process Server
     manually on all the nodes that have the installation.
    If you performed an automatic deployment for the primary node, you do not need to manually deploy on the primary node.
0 COMMENTS
We’d like to hear from you!