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. Customize ActiveVOS
  12. Resource Kit Installation
  13. Resource Kit Post-Installation Tasks
  14. Troubleshooting the MDM Hub
  15. Uninstallation

Installation Guide for IBM Db2 with Red Hat JBoss

Installation Guide for IBM Db2 with Red Hat JBoss

Start the Hub Console

Start the Hub Console

To access the
MDM Hub
, start the
Hub Console
by using an HTTP or HTTPS connection.
Before you start the
Hub Console
, ensure that you have the following information:
  • Host name and port number for the URL
  • User name and password
  • An SSL certificate on the client machine, if you want to access the Hub Console through an HTTPS connection
  1. Open a browser window and enter the following URL:
    http://<
    MDM Hub host
    >:<
    port number
    >/cmx/
    The Hub Console launch page appears.
  2. Enter your user name and password, and then click
    Download
    .
    The MDM Hub application JAR file that is required to launch the Hub Console downloads.
    If you cannot download the MDM Hub application JAR file, contact your MDM administrator. The administrator can distribute the JAR file from the following directory:
    <
    MDM Hub installation directory
    >/hub/server/resources/hub
  3. Run the application JAR file.
    If you do not have an SSL certificate on the client machine, and want to access the
    Hub Console
    through an HTTPS connection, you must install it. To do so, you can use the following procedure:
    • Import the certificate to the Java keystore of your local client machine, by running the following command:
      keytool -import -trustcacerts -alias <certificate alias name> -file <certificate alias file> -keystore <local java cacerts keystore location>
    • Pass the location and password of the truststore file that contains the certificate, by running the following command:
      java -Djavax.net.ssl.trustStore=<truststore file location> -Djavax.net.ssl.trustStorePassword=<truststore_password> -jar hubConsole.jar
      Use a separate truststore that contains all the custom trust certificates, rather than the default cacert file. Obtain the certificates from the team that maintains the application server. The server might use either a self signed certificate or security certificate. Download the .jar file only if there is a version change on the server. Each time you download the .jar file, launch it using the same command.
  4. To specify the maximum memory allocation pool for the application, run the following command:
    java -Xmx<n>G -jar hubConsole.jar
    Where <n> is the maximum memory allocation in GB.
    The
    Informatica MDM Hub Login
    dialog box appears.
  5. Enter your user name and password.
  6. If you want to connect to a specific Hub Server node or if you use a load balancer or a reverse proxy server, override the pre-configured connection parameters in the Connection Property field.
    Enter the parameters in the following format:
    <host name>:<port name>
    Where, host name and port name are either the host name and port name of the Hub Server or that of the load balancer or the reverse proxy server that you use.
  7. Click
    OK
    .
    The
    Change database
    dialog box appears.
  8. Select the target database.
    The target database is the
    MDM Hub Master Database
    .
  9. Select a language from the list, and click
    Connect.
    The
    Hub Console
    user interface appears in the language that you select. If you need to change the language in which the
    Hub Console
    user interface appears, restart the
    Hub Console
    with the language of your choice.

0 COMMENTS

We’d like to hear from you!