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. Seamless Access Setup for Oracle R12 in Data Archive
  21. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  22. Using Multiple Engines in an ILM Environment
  23. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  24. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Keeping the ./webapp/file_archive Directories Synchronized

Keeping the ./webapp/file_archive Directories Synchronized

To manage retention, synchronize the ./webapp/file_archive directory for all Tomcat engines. When you change retention, ILM looks in the Data Vault directory for the DDL of the driving table. If you archive in one instance and then try to manage retention in a different instance, the DDL file will not be found. To ensure that the DDL file can be found, use symbolic links to tie all engines to one base folder.
If you use multiple Tomcat engines and each engine was installed separately, you must synchronize the Data Vault folder and then create the symbolic links to the base archive directory.
For example, you have three ILM engines Prod1, Prod2, and Prod3 and you want to use the Data Vault directory in Prod1 as the base archive directory.
To synchronize the Data Vault folders, complete the following steps:
  1. Go to the ./webapp/file_archive directory in the Prod2 directory.
  2. Copy the contents, including all subdirectories, into the ./webapp/file_archive folder in the Prod1 directory.
  3. Change the Data Vault directory in Prod2 to be a symbolic link to the Data Vault folder in the Prod1 directory.
  4. Go to the ./webapp/file_archive directory in the Prod3 directory.
  5. Copy the contents, including all subdirectories, into the ./webapp/file_archive folder in the Prod1 directory.
  6. Change the Data Vault directory Prod3 to be a symbolic link to the Data Vault folder in the Prod1 directory.
After you set all engines to archive to the same Data Vault directory, enable the informia.dataDiscoveryMetadataQuery parameter so that the metadata for data discovery would be retrieved from the AMHOME schema. Edit the conf.properties file for each instance and set the parameter to informia.dataDiscoveryMetadataQuery=AMHOME.
Effective in ILM 5.3.4, the informia.dataDiscoveryMetadataQuery parameter is set to AMHOME by default.