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 Accelerators

Importing Accelerators

After you export to a set of XML files, you can import them to a different environment. While you run the import job, you specify the job execution mode, the location of the xml metadata files, and the job parameters. By default, when you import an accelerator Data Archive uses the enhanced import option. You can change the import method using the properties given in configuration file.
You can import accelerators as a background job or in the foreground. The background job runs on the Data Archive server instead of on the Enterprise Data Manager client machine. 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. To import accelerators as a background job, you must start Enterprise Data Manager from Data Archive. Standalone Enterprise Data Manager does not support importing as a background job.
When you configure the import job, you can select whether or not to continue processing on error. For custom PFV's, can also select the enhanced import option and choose whether or not to update any existing entities in the custom PFV.
If you selected enhanced export, select enhanced import when you import the custom PFV. Selecting enhanced import allows you to import to the environment without corrupting any data. In addition to enhanced import, you can choose the option to update the entities in the custom PFV, if the entity already exists in the target environment.
When you use enhanced import and choose to update the existing entities, Data Archive first verifies that each entity in the custom PFV has not been implemented in either an archive or retirement project, or in a Data Discovery operation. If an entity has already been implemented in a project or a Data Discovery operation, you receive a message that the entity will not be updated. You can continue with the import of any remaining entities that have not been implemented in a project or a Data Discovery operation. If the entities are not implemented, they are deleted and reinserted.
If you do not select the
Update Existing Entities
checkbox, then the job updates the entities based on the collision check.
By default, the export job uses enhanced import. To change the behavior, configure the following properties in the
conf.properties
file:
  • #informia.enable.enhanced.import=Y
    Enables enhanced import for entities and product family versions. Default is Y. Valid inputs are Y and N.
  • #informia.enable.traditional.import=N
    Enables traditional import. Default is N. Valid inputs are Y and N.
To perform any import operations, a user must have the "import metadata" role assigned in Data Archive. The Administrator user is assigned this role by default, but other users must be assigned this role. For more information on the import metadata role, see the chapter "Security" in the
Data Archive Administrator Guide
.

0 COMMENTS

We’d like to hear from you!