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. How to Create Business Rules to Archive and Purge Transactional Data
  9. How to Uninstall Data Archive 5.1
  10. How to Uninstall Data Archive 5.3
  11. How to Use Scripts to Change Database User Passwords in the ILM Repository
  12. IBM DB2 Database Connectivity and Setup for Data Archive
  13. Installing Data Visualization
  14. Integrating Third-Party Schedulers in ILM Engine
  15. Parallel Processing in Data Archive
  16. Seamless Access Configuration for Siebel Applications
  17. Seamless Access Setup for Oracle E-Business Suite
  18. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  19. Using Multiple Engines in an ILM Environment
  20. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  21. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Description

Description

An environment with multiple ILM Tomcat engines requires only installation. All instances of the user interface will share the same ILM home repository.
To set up multiple Tomcat engines for ILM, complete the following steps:
  • Run the installer to create the initial Tomcat engine and ILM Home schema in the database. For this example, the installation path of the initial engine is /app/dev/ilm/ILM_Engine.
  • Go to the /app/dev/ilm/ILM_Engine directory and zip up the contents of the directory, including subdirectories.
  • Determine how many engines you want to run and create a directory for each. For example, to run two additional engines, you can create the directories /app/dev2/ilm/ILM_Engine and /app/dev2/ilm/ILM_Engine.
  • Copy the zip file you created in step 2 to each of the new directories you created in step 3 and extract the files.
  • For each new instance, change the port number for the Tomcat engine in the conf.properties file. Edit each conf.properties file and search for the property informia.applicationPort. By default, the initial engine uses port number 8080.You can increment the port number by one for each additional engine. For example, use 8081 and 8082 for two additional engines. Verify that the port numbers are not used by other applications.
  • To start each Tomcat engine, run the startApplimation.sh script. Verify that users can access all engines.