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 2
  • 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

Installing the Process Server on Nodes in the Cluster

Installing 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.
When you install the
Process Server
 on RedHat Linux, do not use the root user. The root user does not have a
.profile
, which InstallAnywhere requires. Instead, create and use a separate user profile to install the
Process Server
.
  1. Start the JBoss application server on each cluster node.
  2. Open a command prompt, and navigate to the following directory:
    <
    MDM Hub distribution directory
    >/<
    operating system name
    >/mrmcleanse
  3. Run the following file on each cluster node to start the Process Server installer:
    On UNIX.
    ./hub_cleanse_install.bin
    On Windows.
    hub_cleanse_install.exe
  4. Select the language for the installation, and then click
    OK
    .
    The
    Introduction
     window appears.
  5. Click
    Next
    .
    The
    License Agreement
     window appears.
  6. Select the
    I accept the terms of the License Agreement
     option, and then click
    Next
    .
    The
    Choose Install Folder
     window appears.
  7. Choose the default location to install the Process Server, or browse to choose a different location.
     Click
    Next
    .
    Process Server
     fails to load if the total length of the path exceeds 256 characters or includes spaces in the directory or folder names.
    On UNIX, the
    Choose Link Folder
     window appears.
    On Windows, the
    Choose Shortcut
     Folder window appears.
  8. Select a location for the product icons, and click
    Next
    .
    The
    Enter Location of License File
     window appears.
  9. Click
    Choose
     to select a license file, and click
    Next
    .
    The
    Application Server
     window appears.
  10. Select
    JBoss
    , and then click
    Next
    .
    The
    JBoss Application Server Home
     window appears.
  11. Configure the following JBoss settings:
    1. Specify the application server installation directory, and then click
      Next
      .
      The
      JBoss Application Server Configuration Name
       window appears.
    2. Enter
      standalone
      , and then click
      Next
      .
      The default value is
      standalone
      .
      The
      JBoss Application Server Port
       window appears.
    3. Specify the remote port of the cluster node that is running on the machine.
      The JBoss port can conflict with the default database server port. If ports conflict, change one of the ports to resolve the conflict. For more information on changing ports, see the JBoss documentation.
  12. Configure cleanse engine settings for the cleanse engine you use.
    • If you use
      Informatica Address Verification
      , specify the Configuration file and Parameters file locations and the Correction Type parameter.
    • If you use Business Objects DQ XI, specify the Host, Port, and Sub File parameters for the Business Objects DQ XI cleanse engine.
  13. On the Product Usage Toolkit page, select the
    Environment Type
    .
  14. If you have a proxy server, select
    Yes
    , and enter the proxy server details. Otherwise, select
    No
    , and click
    Next
    .
    You can enter the following proxy server details:
    • Proxy server name/IP
    • Proxy server port
    • Proxy server domain name. Leave blank if not applicable.
    • Proxy server user name. Leave blank if not applicable.
    • Proxy server password. Leave blank if not applicable.
  15. In the
    Deploy
     page, select the
    No, I will run it later
     option, which allows you to manually run the post installation script later.
  16. Click
    Next
    .
    The
    Pre-Installation Summary
     window appears.
  17. After the summary window displays the options you want, click
    Install
     to start the installation process.
    When the installation completes, the
    Install Complete
     window appears.
  18. Choose to restart the system now or later.
  19. Click
    Done
     to exit the
    Process Server
     installer.
  20. Restart the JBoss application server on each cluster node.
0 COMMENTS
We’d like to hear from you!