Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  21. Using Multiple Engines in an ILM Environment
  22. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  23. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Configuring Data Archive for a Legacy Source Using Legacy Adapters

Configuring Data Archive for a Legacy Source Using Legacy Adapters

  1. Install the legacy application adapter.
  2. Start the legacy application adapter.
    In most cases, you can start the adapter with security turned off.
  3. Configure the legacy application adapter.
  4. Mine the legacy source tables in the legacy application adapter.
  5. Mine the legacy application adapter synonyms in EDM.
    Use the legacy application adapter in the platform list of EDM. (Default username and password: edadb/edadb)
  6. Create the staging tables on the source.
    If you cannot create the staging tables on the legacy source, create the staging schema on the same database as AMHOME.
  7. Create the staging table on AMHOME.
    This step is only required if you have business rules or if you will create interims for your entity for archiving based on parameters.
  8. Create adapter to AMHOME on the legacy application adapter.
  9. Mine the staging tables in the legacy application adapter.
  10. Create the source repository with "No" for "Use Staging" and "No" for "Parallel Entity Run."
    Leave this property unchecked to ensure that the engine does not create job-specific interims. The engine uses what you created in steps 7-9.
  11. Run the archive and purge cycle.
    As long as the where clause for insert and delete is "sql92," you should be fine.