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

Identifying Retirement Application

Identifying Retirement Application

As a first step to application retirement, the information to be specified is described in the following table:
Application Detail
Description
Application Name
A name for an application is mandatory.
Application Vendor Name
Vendor name of the selected application.
Application Owner
Application owner of the legacy application selected.
Vendor Contact
Contact information of the vendor.
Retirement Date
A mandatory field to enter proposed retirement date.
Vendor Phone
Vendor contact numbers.
Primary Contact
Vendor's primary contact information.
Vendor Contract Number
The signed contract number of the vendor.
Comments
A section where additional information related to this particular retirement can be added.
The Add More Attributes button
A facility to add any more attributes that you may want to include to the application details which would serve in the process of application retirement.
Use Integrated Validation
Enables integrated validation for the project.
Use 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 in case the job fails and must be resumed. When you run the retirement job, the key is passed to Data Vault as a job parameter and is not stored in Data Vault or any log file. If the retirement job is successful, the key is deleted from the ILM repository. The encrypted key is unique to the retirement definition and is generated only once for a definition.
If you have enabled data encryption for both the selected target connection and the retirement definition, Data Archive uses the retirement 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.
Clicking the Next button advances to the section on defining source and target repositories. The Save Draft button saves the project for future modifications and scheduling.

0 COMMENTS

We’d like to hear from you!