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 as a Background Job

Importing as a Background Job

You can import accelerators, custom PFV's, and entities as a background job. The background job runs on the Data Archive server instead of on the Enterprise Data Manager client machine.
To import accelerators, custom PFV's, or entities as a background job, you must start the Enterprise Data Manager from Data Archive. The standalone version of the Enterprise Data Manager does not support offline import.
You may want to run the job on the Data Archive server to improve the job performance and to reduce the amount of resources consumed on the Enterprise Data Manager client machine. Run on the Data Archive server to avoid memory-related issues if you need to import a large volume of metadata.
You can import XML files only when the export and import environments are on same version of Data Archive. If you used enhanced export to export an XML file through a previous version of Data Archive, you cannot import the same XML file in version 6.4.4. Only XML files exported through version 6.4.4 can be imported in version 6.4.4.
If you used traditional export to export the metadata files, you cannot import them using the enhanced import option. Use the same type of import as export.
  1. Click
    File
    Import
    Accelerators
    The
    Import Metadata Options
    screen appears.
  2. Choose
    Submit Import Metadata as a Background Job
    .
  3. Select the machine and location of the .xml metadata files.
    • Location on Server. Select if the .xml metadata files exist on the Data Archive server. Enter the full path to the files. For example,
      /home/oracle/ILM/export
    • Location on Client. Select if the .xml metadata files exist on the EDM client machine. Click
      Browse
      to navigate to the directory.
    If you specify the directory that you exported to during the export job, the import job will fail because the export job saves the exported metadata in sub-directories within the directory that you specified during export. The sub-directories have a timestamp as the name. When you select the directory to import, give the full file path including the sub-directory.
  4. Configure the job parameters. If you used the enhanced export option to export the data, select
    Enhanced Import
    .
  5. Click
    OK
    .
    The system immediately runs the job in the background and provides a message that the job was submitted. The message includes the job ID. You can monitor the job status in Data Archive.

0 COMMENTS

We’d like to hear from you!