Table of Contents

Search

  1. Preface
  2. Introduction
  3. Working with Enterprise Data Manager
  4. Enterprise Data Manager
  5. ILM Repository Constraints
  6. Partition Exchange Purging
  7. APIs
  8. Smart Partitioning
  9. Salesforce Accelerator
  10. SAP Application Retirement Entities
  11. Import Formats for Constraints
  12. Glossary

Enterprise Data Manager Guide

Enterprise Data Manager Guide

Importing Metadata from the Database

Importing Metadata from the Database

Import metadata from the source database to the ILM repository. You must import metadata before you can run an archive or retirement job.
For SAP application retirement, you must initiate the metadata import from a customer-defined application. Run the Copy Application Version for Retirement job to copy the pre-packaged SAP application to a customer-defined application.
To import metadata from any database, a user must have the Import Metadata system-defined role. For more information, see the
Data Archive Administrator Guide
.
You must also configure the "informia.enable.mining" property in the
conf.properties
file. For more information, see the
Data Archive Administrator Guide
.
  1. Select an application version and click
    File
    Import Metadata from Database
    .
    The
    Connect to Import Metadata from Database
    dialog box appears.
  2. Enter the connection details.
    To create a connection for Informix sources, use the following syntax for the service name:
    <server_name>;databasename=<dbname>
  3. Click
    OK
    .
    The
    Import Metadata from Database Wizard
    appears.
  4. Select the schemas to import metadata from.
    Click the down arrow button to insert the tables in to the Selected box. Use the control keyboard options to select multiple tables or all tables.
    Tables that have special characters in the table name, do not appear in the list. Special characters include:
    ~
    ,
    !
    ,
    @
    ,
    #
    ,
    $
    ,
    ?
    ,
    %
    ,
    ^
    ,
    &
    ,
    *
    ,
    _
    ,
    +
    ,
    -
    , and
    =
    .
  5. Click
    Next
    .
  6. Choose one of the following options to run the job:
    • Submit Import Metadata as a Background Job
      . Runs the job in the background. If you run the job in the background, you can continue to perform other tasks. Run the job in the background if you have a large volume of metadata to import and to avoid memory errors.
      Required to import metadata from SAP applications.
    • Continue Import Metadata through EDM
      . Runs the job in the foreground. If you run the job in the foreground, you must wait until the job completes to perform an other task. Additionally, if you run the job in the foreground and you have a large volume of metadata to import, you may receive memory errors. You may want to run the job in the foreground if you have a low volume of metadata to import.
  7. Click
    Next
    .
  8. Enter the mining parameters.
    To import metadata from databases for SAP applications, select
    SAP Application Metadata
    . The Import Metadata job runs steps that are specific to SAP applications. If you import from SAP applications and do not select the parameter, the job will not import metadata for pool tables, cluster tables, and tables that store data in ADK files.
  9. Click
    Finish
    .
  10. Click
    OK
    .

0 COMMENTS

We’d like to hear from you!