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

Create the MDM Hub Master Database

Create the MDM Hub Master Database

After you install IBM Db2, create an
MDM Hub Master Database
.
If you want to create multiple MDM Hub Master Databases, ensure that you create each MDM Hub Master Database in a different schema.
The default name of the MDM Hub Master Database is
CMX_SYSTEM
, but you can use a custom name.
If you change the folder names in the distribution directory, metadata import fails.
  1. Open a command prompt, and navigate to the following directory:
    <
    MDM Hub distribution directory
    >/database/bin
  2. To create the MDM Hub Master Database, run the following command:
    On UNIX.
    ./sip_ant.sh create_system
    On Windows.
    sip_ant.bat create_system
  3. Answer the prompts described in the following table:
    The prompt displays default text in brackets. Press
    Enter
    to use the default value and go to the next prompt.
    Prompts
    Description
    Enter the database type (ORACLE, MSSQL, DB2)
    Database type.
    Specify
    DB2
    .
    Db2 datasources are case-sensitive. To avoid issues related to case-sensitivity, Informatica recommends that you use uppercase letters to define names, such as the schema names, column names, and triggers.
    Enter the database host name [localhost]
    Name of the host that runs the database. Default is
    localhost
    .
    In cluster environments, specify the absolute host name or the IP address to avoid caching issues.
    Enter the database port number
    [50000]
    Port number that the database listener uses.
    Default is
    50000
    .
    You cannot create the Db2 database if the port number is not the default 50000. You must manually change the port number in the Db2 properties file.
    Enter the database instance name [SIP97]
    Name of the database instance. Default is
    SIP97
    .
    Enter master database name [cmx_system]
    Name of the MDM Hub Master Database schema. Default is
    cmx_system
    .
    Enter master user name [cmx_system]
    User name to access the MDM Hub Master Database. Default is
    cmx_system
    .
    Enter master database user password
    Password to access the MDM Hub Master Database.
    Enter locale name from the list: de, en_US, fr, ja, ko, zh_CN. [en_US]
    Operating system locale. Default is
    en_US
    .
    Enter the DBA user name
    [DB2ADMIN]
    User name of the administrative user.
    Default is
    DB2ADMIN
    .
    Enter the DBA password
    Password of the administrative user.
  4. To verify that the MDM Hub Master Database was created successfully, review
    sip_ant.log
    in the following directory:
    <
    MDM Hub distribution directory
    >/database/bin
    The
    sip_ant.log
    file logs any errors that might occur when you run the
    sip_ant
    script to create the
    MDM Hub Master Database
    .
  5. If you intend to configure single sign-on authentication for other applications such as Salesforce, increase the BLOB column length. Run the following command on the MDM Hub Master Database:
    SET SCHEMA CMX_SYSTEM; ALTER TABLE C_REPOS_SAM_PROVIDER_FILE ALTER COLUMN PROVIDER_FILE SET DATA TYPE BLOB (10240000); CALL ADMIN_CMD('REORG TABLE C_REPOS_SAM_PROVIDER_FILE');

0 COMMENTS

We’d like to hear from you!