Enterprise Data Manager Guide

6.5 HotFix 1
- 6.5.1
- 6.5
- 6.4.4
- 6.4.3 HotFix 1
- 6.4.3

Back Next

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 might 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 the job 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.

Click

File

Import

Accelerators

The

Import Metadata Options

screen appears.

Choose

Submit Import Metadata as a Background Job

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 Enterprise Data Manager 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 fails because the export job saves the exported metadata in subdirectories within the directory that you specified during export. The subdirectories have a timestamp as the name. When you select the directory to import, give the full file path including the subdirectory.

Configure the job parameters. If you used the enhanced export option to export the data, select

Enhanced Import

Click

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.

Rename Saved Search

Table of Contents

Enterprise Data Manager Guide

Enterprise Data Manager Guide

Importing as a Background Job

Importing as a Background Job