Table of Contents

Search

  1. Preface
  2. Introduction
  3. Accessing Data Archive
  4. Working with Data Archive
  5. Scheduling Jobs
  6. Viewing the Dashboard
  7. Creating Data Archive Projects
  8. Salesforce Archiving
  9. SAP Application Retirement
  10. Creating Retirement Archive Projects
  11. Integrated Validation for Archive and Retirement Projects
  12. Retention Management
  13. External Attachments
  14. Data Archive Restore
  15. Data Discovery Portal
  16. Data Visualization
  17. Oracle E-Business Suite Retirement Reports
  18. JD Edwards Enterprise Retirement Reports
  19. Oracle PeopleSoft Applications Retirement Reports
  20. Smart Partitioning
  21. Smart Partitioning Data Classifications
  22. Smart Partitioning Segmentation Policies
  23. Smart Partitioning Access Policies
  24. Language Settings
  25. Appendix A: Data Vault Datatype Conversion
  26. Appendix B: Special Characters in Data Vault
  27. Appendix C: SAP Application Retirement Supported HR Clusters
  28. Appendix D: Glossary

Target

Target

When you create an archive project, you choose the target connection and configure how the job archives data to the target. You can archive to the Data Vault or to another database.
Archive to the Data Vault to reduce storage requirements and to access the archived data from reporting tools, such as the Data Discovery portal. Archive to another database to provide seamless data access to the archived data from the original source application.
For archive jobs that include
archive only
and
archive and purge
cycles, the system validates that the connections point to different databases. If you use the same database for the source and target connections, the source data may be duplicated or deleted.
The following table describes properties for Data Vault targets:
Property
Description
Connection Name
List of target connections. The target connection includes details on how the archive job connects to the target database and how the archive job processes data for the target.
Choose the Data Vault target that you want to archive data to. This field is mandatory.
Include Reference Data
Select this option if you want the archive project to include transactional and reference data from ERP tables.
Reference Data Store Connection
Required when you use a history database as the source.
Connection that contains the original source reference data for the records that you archived to the history database. The source includes reference data that may not exist in the history database. The archive job may need to access the reference data when the job archives or purges from the history database.
Enable Data Encryption
Select this option to enable data encryption on the compressed Data Vault files during load. If you select this option, you must also choose to use a random key generator provided by Informatica or your choice of a third-party key generator to create an encryption key. Data Archive stores the encrypted key in the ILM repository as a hidden table attribute. When you run the archive definition, the key is passed to Data Vault as a job parameter and is not stored in Data Vault or any log file. The encrypted key is unique to the archive definition and is generated only once for a definition. If you run an archive definition more than once, the same encryption key is used.
If you have enabled data encryption for both the selected target connection and the archive definition, Data Archive uses the archive definition encryption details. If you do not configure data encryption at the definition level, then the job uses the details provided at the target connection level.
Use Random Key Generator
Option to use a random key generator provided by Informatica when data encryption is enabled. When you select this option, the encryption key is generated by a random key generator provided by Informatica (javax.crypto.KeyGenerator).
Use Third Party
Option to use a third-party key generator when data encryption is enabled. If you select this option, you must configure the property "informia.encryptionkey.command" in the
conf.properties
file. Provide the command to run the third-party key generator.
The following table describes properties for database targets:
Property
Description
Connection name
List of target connections. The target connection includes details on how the archive job connects to the target database and how the archive job processes data for the target.
Choose the database target that you want to archive data to.
Seamless Access Required
Select this option if you want to archive to a database repository at the same time as you archive to the Data Vault server.
Allows seamless access to both production and archived data.
Seamless Access Data Repository
Repository that stores the views that are required for enabling seamless data access.
Commit Interval (For Insert)
Number of database insert transactions after which the archive job creates a commit point.
Parallelism Degree (Delete)
Number of concurrent threads for parallel deletions.
Parallelism Degree (Insert)
Number of concurrent threads for parallel insertions.
The available fields depend on the type of archive cycle you select. After you configure the target, you can continue to configure the project details or save the project.
Click
Next
to add entities to the project.
Click
Save Draft
to save a draft of the project. You can edit the project and complete the rest of the configuration at a later time.

0 COMMENTS

We’d like to hear from you!