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 1
  • 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 Hub Server on Nodes in a Cluster

Installing the Hub Server on Nodes in a Cluster

In application server cluster environments, install the Hub Server on all the nodes of the cluster to which you must deploy the Hub 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 Hub Server on node1 and node2. You must complete the Hub 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 Hub Server installation is the same on all the nodes.
  1. Start the JBoss cluster nodes on which you want to install the Hub Server.
  2. Open a command prompt, and navigate to the following directory:
    <
    MDM Hub distribution directory
    >/<
    operating system name
    >/mrmserver
  3. To start the Hub Server installer on a cluster node, run the following command:
    On UNIX.
    ./hub_install.bin
    On Windows.
    hub_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 an Install Folder
     window appears.
  7. Select the location of the
    Hub Server
     installation.
    • To choose the default location, click
      Next
      .
    • To enter a path, type the path to the installation folder, and click
      Next
      .
      The installation fails if you specify a path that has spaces in the directory or folder names.
    • To choose another location, click
      Choose
      , and then click
      Next
      .
  8. On UNIX, choose a link folder or select the option to not create links and click
    Next
    .
    On Windows, select the location to create a product icon or select the option not to create a product icon.
  9. Click
    Next
    .
    The
    Enter the location of the license file
     window appears.
  10. Click
    Choose
     to select a license file, and click
    Next
    .
    The
    Advanced Security
     window appears.
  11. Select
    JBoss
    , and then click
    Next
    .
    The
    JBoss Application Server Home
     window appears.
  12. 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.
    4. Specify the native management port.
      Default is
      9990
      . If port offset is configured for the application server, add the offset value to the default value.
      For example, if the port offset is
      100
      , the native management port value is
      10090
      , which is (9990 + 100).
  13. Click
    Next
    .
    The
    Database Selection
     window appears.
  14. Select IBM DB2 UDB, and click
    Next
    .
    The
    DB2 Database Information
     window appears.
  15. Enter the following settings for the IBM DB2 database to which you want to connect, and click
    Next
    :
    Field Name
    Description
    Server
    Host name of the
    MDM Hub Master Database
     server.
    Port
    Port number of the
    MDM Hub Master Database
    .
    Database Name
    Name of the database that you created.
    System Schema
    Name of the
    MDM Hub Master Database
    .
    System Schema User Name
    The IBM DB2 database user that you use to access the system schema.
    Use the same user that you used to import seed into the
    MDM Hub Master Database
    .
    System Schema Password
    Password of the user used to connect to the system schema.
    The
    Install ActiveVOS
     window appears.
  16. If you want to install the bundled, licensed version of
    Informatica ActiveVOS
    , select
    Yes
     and perform the following substeps. Otherwise, select
    No
    , and click
    Next
    .
    1. On the
      Choose ActiveVOS Installation Folder
       page, accept the default installation path or specify a preferred location. Click
      Next
      .
    2. On the
      Database Information
       page, enter the database details that you specified when you created the ActiveVOS database schema, and click
      Next
      .
    3. On the
      Application Server Web URL
       page, accept the default URL or specify the URL that you want to use to call ActiveVOS web services. Ensure the URL contains the correct port number for the connection to the application server. Click
      Next
      .
      The post installation setup script uses the URL to call ActiveVOS web services, deploy the predefined MDM workflows to ActiveVOS, and create the URN mapping.
    4. On the
      ActiveVOS Installer
       page, click
      Choose
       and browse to the ActiveVOS_Server installation file in the distribution package. Click
      Next
      .
    5. Enter the administrative user name and password to create an administrative user for the ActiveVOS Console.
      The user name and password must be the same as the ActiveVOS Console user name and password that was created in the application server.
    6. Click
      Next
      .
  17. Select one of the following Informatica platform installation options:
    • Yes
      . Install Informatica platform.
    • No
      . Does not install Informatica platform.
  18. If you select
    Yes
     in the preceding step, click
    Choose
     and browse to the following Informatica platform file locations:
    • Installation response file
    • Platform installation file
  19. On the Product Usage Toolkit page, select the industry to which the organization belongs and the environment type.
  20. If you want to use a proxy server, select
    Yes
    , and enter the proxy server details. Otherwise, select
    No
    .
    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.
  21. Click
    Next
    .
    The Deploy page appears.
  22. Select the
    No, I will run it later
    postInstallSetup
     script option.
    The installer does not run the
    postInstallSetup
     script during the installation. Ensure that you manually deploy the Hub Server applications after the installation.
  23. Click
    Next
    .
    The
    Pre-Installation Summary
     window appears.
  24. After the Pre-Installation Summary window displays the options you want, click
    Install
     to start the installation process.
    When the installation completes, the
    Install Complete
     window appears.
  25. Click
    Done
     to exit the Hub Server installer.
You can use any node in the JBoss cluster to access the Hub Server.
0 COMMENTS
We’d like to hear from you!