Table of Contents

Search

  1. Preface
  2. Introduction to Enterprise Data Manager
  3. Enterprise Data Manager
  4. ILM Repository Constraints
  5. Partition Exchange Purging
  6. APIs
  7. Salesforce Accelerator
  8. Appendix A: SAP Application Retirement Entities
  9. Appendix B: Import Formats for Constraints
  10. Appendix C: Glossary

Enterprise Data Manager Guide

Enterprise Data Manager Guide

Importing Metadata from the Database

Importing Metadata from the Database

Before you can run an archive or retirement job, you must import metadata from the source database to the ILM repository.
To import metadata from a database, ensure the following prerequisites are in place:
  • You have the Import Metadata system-defined role.
  • You set the
    informia.enable.mining
    property file to Y in the
    conf.properties
    file.
For more information, see the
Data Archive Administrator Guide
.
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 prepackaged SAP application to a customer defined application.
To import metadata from the source database to the ILM repository, perform the following steps:
  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>
    If the connection type is a Microsoft SQL Server, provide the following attributes:
    Database_Port=
    xxxx
    ;encryptionMethod=SSL;ValidateServerCertificate=false/true;CryptoProtocolVersion=TLSv1.2
    Where
    xxxx
    is the port number. For example:
    Database_Port=1433;encryptionMethod=SSL;ValidateServerCertificate=false/true;CryptoProtocolVersion=TLSv1.2
    CryptoProtocolVersion is the name of the protocol supported by the database server.
    If the database type is Oracle 11g, 12c, or 18c, the following options are available:
    Oracle Database Type
    Options
    Oracle 11g, 12c, or 18c
    SSL Enabled
    . Establish an SSL connection to the Oracle database.
    To use SSL, you must add the SSL certificate of the Oracle server to the respective Java
    cacerts
    file where Enterprise Data Manager is running.
    Advanced Security Options (ASO)
    • ASO Encryption Level
    • ASO Encryption Type
    • ASO Checksum Level
    • ASO Checksum Type
    You cannot use SSL and ASO options together. If you enable SSL, ASO options are not available. For more information, see the
    Data Archive Administrator Guide
    .
    Oracle 11g or 12c
    OID Enabled
    . Establish a connection through an OID database, to the internal Oracle database. Enter the OID database host name in the
    Host
    field. Enter the service name in the
    Service Name
    field. The service name specifies the distinguished name of the database, which is configured in OID.
    For example:
    Servicename = ORA12C,cn=OracleContext,dc=informatica,dc=com
    You cannot use OID and ASO options together. When you enable OID, ASO options are not available.
  3. Click
    OK
    .
    The
    Import Metadata from Database Wizard
    appears.
  4. Select the schemas to import metadata from.
    To insert the tables into the
    Selected
    box, click the down arrow. To select multiple tables or all tables, use the control keyboard options.
    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 other tasks. Additionally, if you run the job in the foreground and you have a large volume of metadata to import, you might receive memory errors. Consider running 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!