Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Supplier 360
  3. Supplier 360 Installation Overview
  4. Before You Install
  5. Installing the Supplier 360 Components
  6. After You Install
  7. Business Processes for Supplier Management
  8. Customizing Supplier 360
  9. Upgrading MDM - Supplier 360

Importing the MDM Metadata

Importing the MDM Metadata

After you create the supplier_hub Operational Reference Store, import the MDM metadata into the Operational Reference Store.
  1. Navigate to the following directory:
    <MDM installation directory>/hub/server/bin
  2. Run one of the following commands:
    • On Windows.
      sip_ant.bat import_ors
    • On Linux.
      sip_ant.sh import_ors
  3. Enter values for the Operational Reference Store parameters.
    The prompts display default text in brackets. Press
    Enter
    to use the default value and go to the next prompt.
    Parameter
    Description
    Database Type
    Enter Oracle.
    Oracle Connection Type
    Enter the type that you specified for the Oracle database instance.
    Operational Reference Store DB host name
    Enter the IP address of the host running Oracle.
    Operational Reference Store DB port number
    Enter the port number that Oracle uses.
    Operational Reference Store DB service name
    If the Oracle Connection Type=service, enter the name of the Oracle service that you specified for the Oracle database instance.
    Oracle Net connect identifier
    Enter the TNS name that you specified for the Oracle database instance.
    Connect URL
    Use the default URL unless you are required to change the URL for business reasons or technical reasons.
    Operational Reference Store DB user name (schema name)
    Enter
    supplier_hub
    .
    Operational Reference Store DB user password
    Enter the password for the supplier_hub user.
    Locale name
    Enter the language to use.
    DBA user name
    Enter the user name for the Oracle database instance.
    DBA password
    Enter the password for this user.
    Timeline granularity
    Enter the timeline units to use.
    After the database schema is imported, you cannot change the timeline granularity.
    The script triggers the process that loads the metadata into the Operational Reference Store.
  4. If the process fails, check the log files for errors. You can find log files in the following locations:
    • User input errors.
      <MDM installation directory>/hub/server/bin/sip_ant.log
    • Database errors.
      <MDM installation directory>/hub/server/bin/<database type>/seed.log

0 COMMENTS

We’d like to hear from you!