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

Installing the Hub Server in Console Mode

Installing the Hub Server in Console Mode

You can install the
Hub Server
 in console mode on UNIX.
  1. Start the application server.
  2. Open a command prompt, and navigate to the following directory in the MDM Hub distribution:
    <
    MDM Hub distribution directory
    >/<
    operating system name
    >/mrmserver
  3. Run the following command: 
    ./hub_install.bin -i console
  4. Enter the number of the locale you want to choose for the installation, and then press
    Enter
    .
    The introduction information about the installation appears.
  5. Press
    Enter
    .
    The license agreement appears.
  6. Read the License Agreement. Type
    Y
     to accept the terms of the license agreement, or type
    N
     if you do not want to accept the license agreement and want to exit the installation program.
  7. Press
    Enter
    .
    If you entered
    Y
     in the preceding step, information about the installation folder appears.
  8. Choose a folder for the
    Hub Server
     installation.
    • To choose the default folder, press
      Enter
      .
    • To change the path, type the absolute path of the installation folder, and press
      Enter
      .
  9. Confirm the location of the installation folder. Type
    Y
     to confirm the installation folder, or type
    N
     to change the installation folder.
  10. Press
    Enter
    .
    A list of link location options appears.
  11. Enter the number of a link location option.
    The prompt for the license file location appears.
  12. Enter the absolute path of the license file, and press
    Enter
    .
    A list of advanced security options appears.
  13. Choose a security configuration for the MDM Hub.
    • To choose the default configuration, press
      Enter
      .
    • To choose a custom security configuration for the MDM Hub, type
      Custom
      , and press
      Enter
      .
    • When prompted for a customer hash key, you can enter a value up to 128 bits.
  14. If you typed Custom in the preceding step, choose one of the following options:
    • To accept the default hashing algorithm for password hashing in the MDM Hub, press
      Enter
      .
    • To choose a custom hashing algorithm, type
      Other
      , and press
      Enter
      .
  15. If you typed Other in the preceding step, provide the following information for the custom hashing algorithm:
    • Hashing algorithm name
    • Location of the hashing algorithm archive.
      The hashing algorithm archive must be a ZIP file. If the archive contains multiple JAR files and other supporting files, ensure they are all in the ZIP file.
    • Canonical class name of the hashing algorithm implementation.
      For example, enter
      $HASHING_CLASS_NAME$
      .
    A list of certificate provider options appears.
  16. To select the certificate provider for the MDM Hub to authenticate trusted applications, choose one of the following options:
    • To choose the default certificate provider, press
      Enter
      .
    • To choose a custom certificate provider, type
      Custom
       and press
      Enter
      .
  17. If you typed Custom in the preceding step, provide the following information for the custom certificate provider:
    1. Enter the location of the certificate provider archive.
      The certificate provider archive must be a ZIP file. If you use a custom certificate provider, ensure the
      <
      MDM Hub installation directory
      >/server/resources/certificates
       directory is empty. In a WebSphere environment, the MDM Hub user must also have access and write permissions for the certificates directory.
    2. Enter the class name of the certificate provider, and then press
      Enter
      .
    A list of application server options appears.
  18. Enter the number for the application server that you want to select, and press
    Enter
    .
    The application server information appears.
  19. Configure the JBoss settings.
    1. Specify the application server installation directory, and press
      Enter
      .
      The JBoss application server configuration name information appears.
    2. Specify the configuration name. The default value is
      standalone
      .
    3. Press
      Enter
      .
    4. Specify the remote port.
      If the JBoss port conflicts with the default database port, then change one of the ports to resolve the conflict.
    5. Specify the native management port, and press
      Enter
      .
      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).
  20. Press
    Enter
    .
    The database selection prompt appears.
  21. Select IBM DB2 UDB, and press
    Enter
    .
  22. Specify the settings for the DB2 database to which you want to connect.
    Press
    Enter
     to accept the default values, or replace the defaults with the correct values.
    The following table describes the prompts:
    Prompt
    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
    User belonging to the DB2ADMNS user group 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.
  23. Press
    Enter
    .
  24. If you want to install the bundled, licensed version of the ActiveVOS Server, press
    Enter
     for Yes. Otherwise, type
    2
     for No and press
    Enter
    .
    If you selected Yes, the installer prompts you to provide information about your ActiveVOS installation.
    1. Specify the location where you want to install the ActiveVOS Server.
    2. Specify the URL that you want to use to call MDM and ActiveVOS web services.
    3. Enter information about the ActiveVOS database that you specified when you created the ActiveVOS schema.
    4. Specify the location of the ActiveVOS Server installation file.
    5. Enter a user name and password to create an administrative user for the ActiveVOS Server Administration 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.
  25. Press
    Enter
    .
    The Informatica platform installation prompt appears.
  26. If you want to install the Informatica platform, press
    Enter
     for Yes. Otherwise, type
    2
     for No and press
    Enter
    .
    The prompts for the Informatica platform installation response file and archive file locations appear.
  27. Enter the locations of the Informatica platform installation response file and archive file, and press
    Enter
    .
  28. Specify the Product Usage Toolkit options.
    1. Enter the industry to which the organization belongs , and then press
      Enter
      .
    2. Enter the environment type. Type
      1
       for Production, type
      2
       for Test/QA, or type
      3
       for Development, and then press
      Enter
      .
  29. Select whether you have a proxy server. Press
    Enter
     for Yes. Otherwise, type
    2
     for No and then press
    Enter
    .
    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.
    The summary of the installation choices appears.
  30. Choose whether you want to run the
    postInstallSetup
     script as part of the installation, or run it manually later.
    In a WebLogic 12.2.1.3 or later environment, if you decided to install ActiveVOS or if you decided to use the WebLogic T3S protocol, select
    No, I will run it later
    .
  31. Verify the information in the pre-installation summary. If the information is correct, press
    Enter
     to start the installation.
    The Hub Server is installed according to the configuration information you provide. When the process is complete, the installation complete message appears.
  32. Press
    Enter
     to exit the installer.
0 COMMENTS
We’d like to hear from you!