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

Security

Security

You can create the following optional config file to restrict access to the Transaction Restore API: txnrestore-api.properties.
Save the file to the \WEB-INF directory.
In this file you can supply a parameter called "validHosts", in which you can supply a comma separated list of hostnames, IP Addresses, or Regular Expressions of either. For Example:
validHosts=host1, 192.168.168.97, dev.*
In the example above, the following machines have access to the Transaction Restore API:
  • Any machine named "host1." (The host name is derived from DNS reverse lookup or from the webserver.)
  • The machine with IP address 192.168.168.97.
  • Any machine with a name that starts with "dev." (The host name is derived from DNS reverse lookup or from the webserver.)
Effective in version 5.3.3 HotFix 2, the txnrestore-api.properties file is deprecated. Modify the validHosts property in the conf.properties file.
Effective in version 5.3.4, the default security changed. By default, only the machines that you configure as valid hosts in the conf.properties file are authorized to call the JavaServer page API. Previously, if you did not configure valid hosts, then any IP address or host could call the JavaServer page API.