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:
Go to the ./webapp/file_archive directory in the Prod2 directory.
Copy the contents, including all subdirectories, into the ./webapp/file_archive folder in the Prod1 directory.
Change the Data Vault directory in Prod2 to be a symbolic link to the Data Vault folder in the Prod1 directory.
Go to the ./webapp/file_archive directory in the Prod3 directory.
Copy the contents, including all subdirectories, into the ./webapp/file_archive folder in the Prod1 directory.
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.