Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Archive 6.5 HotFix 1
  • All Products

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. Data Privacy
  18. Oracle E-Business Suite Retirement Reports
  19. JD Edwards Enterprise Retirement Reports
  20. Oracle PeopleSoft Applications Retirement Reports
  21. Language Settings
  22. Data Vault Datatype Conversion
  23. Special Characters in Data Vault
  24. SAP Application Retirement Supported HR Clusters
  25. Glossary

User Guide

User Guide

Back Next

Prerequisites

Prerequisites

Before you can run a Data Visualization report, you must first retire the JDEdwards Enterprise application.
To retire a JD Edwards Enterprise application, perform the following high-level tasks:
  1. In the Enterprise Data Manager, create a customer-defined application version.
  2. Import metadata from the JD Edwards application to the customer-defined application version.
  3. Create retirement entities. Use the generate retirement entity wizard to automatically generate the retirement entities.
  4. In the Data Archive user interface, create a source connection. For the connection type, choose the database in which the JD Edwards application is installed.
  5. Configure the JD Edwards application login properties.
  6. Create a target connection to the Data Vault.
  7. Run the create archive folder standalone job to create archive folders in the Data Vault.
  8. Create and run a retirement project.
  9. In the Enterprise Data Manager, create constraints for the imported source metadata in the ILM repository. Constraints are required for Data Discovery Portal searches. The JD Edwards application retirement accelerator includes constraints for some tables in the JD Edwards system. You might need to define additional constraints for tables that are not included in the accelerator.
  10. Copy the entities from the pre-packaged JD Edwards application version to the customer-defined application version. To copy the entities, perform the following high-level steps:
    After you install the JD Edwards retirement report accelerator, the report entities and application modules appear underneath the JD Edwards Retirement application 1.0.
    • If you imported the application metadata from a single schema
       to the customer-defined application version:
    1. Right click on the customer-defined application version where you imported the metadata and select
      Copy Entities from Application Version
      .
      The
      Copy Entities from Application Version
       window appears.
    2. Select the application version from where you need to copy, which is typically JD Edwards Retirement 1.0.
    3. Provide the prefix that will be appended before the entity while copying. The Copy All Entities option is not required.
    4. Click
      OK
      .
    5. After you submit the background job, you can view the job status from the Data Archive user interface. Once the job successfully completes, you can view the copied entities in your customer-defined application version. You can use these entities for Data Discovery.
    • If you imported the application metadata from multiple schemas
       to the customer-defined application version, you must march the schema names and the application module names in the ILM repository to the pre-packaged JD Edwards application version names. To map these names, you must manually update the ILM repository. After you copy the entities, you will revert back to the original names.
    The pre-packaged JD Edwards application version has two schemas: TESTDTA and TESTCTL. The TESTCTL schema has one table called "F0005." The remaining tables are from TESTDTA.
    1. Run the following update statements: 
      /* identify your custom-defined product family version id*/
SELECT * FROM AM_PRODUCT_FAMILY_VERSIONS; 
/* identify schema id’s of custom-defined product family version*/
SELECT * FROM AM_META_SCHEMAS WHERE PRODUCT_FAMILY_VERSION_ID= < pfv id>; 
UPDATE AM_META_SCHEMAS SET META_SCHEMA_NAME='TESTCTL' WHERE META_SCHEMA_ID=<Schema id of F0005 table>;
UPDATE AM_META_SCHEMAS SET META_SCHEMA_NAME='TESTDTA'  WHERE META_SCHEMA_ID=<Schema id of remaining tables>;
    2. Create the metadata application modules to map to the JD Edwards retirement application modules. Right-click on the application version and select
      New Application Module
      .
      The
      Application Module Wizard
       window appears.
    3. Enter the application module name to match the source name.
    4. Repeat the naming process for all of the modules.
    5. Right-click the product family version where the tables are imported and retired.
    6. Select
      Copy Entities from Application Version
      .
      The
      Copy Entities from Application Version
       window appears.
    7. Select the application version from where you need to copy, typically JD Edwards Retirement 1.0.
    8. Provide the prefix that will be appended before the entity while copying. The Copy All Entities option is not required.
    9. Click
      OK
      .
    10. After you submit the background job, you can view the job status from the Data Archive user interface. Once the job successfully completes, you can view the copied entities in your customer-defined application version. You can use these entities for Data Discovery and retention.
    11. Once the copy process is complete, revert the updates you made in step a.
    In JD Edwards applications, dates are stored in Julian format which is 5 or 6 digits. When you search on columns with date values in Data Discovery, select data conversion from Julian data to Gregorian data in the available search options.
    To update a retention policy, use the following conversion from Julian to Gregorian as an expression: 
    (CASE WHEN length(char(dec(F43199.OLUPMJ))) = 5 THEN date('1900-01-01') + int(left(char(int(F43199.OLUPMJ)),2)) years + int(right(char(int(F43199.OLUPMJ)),3))-1 days ELSE date('1900-01-01') + int(left(char(int(F43199.OLUPMJ)),3)) years + int(right(char(int(F43199.OLUPMJ)),3))-1 days END)
  11. Before you run the reports, copy the report templates to the folder that corresponds to the Data Vault connection. You can use these pre-packaged Data Visualization reports to access retired data in the Data Vault. When you copy the reports, the system updates the report schemas based on the connection details.
  12. Optionally, validate the retired data.
  13. After you retire and validate the application, use the Data Discovery Portal, Data Visualization reports, or third-party query tools to access the retired data.
0 COMMENTS
We’d like to hear from you!