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

API Parameters

API Parameters

The API needs to receive the following items:
  • Definition ID. This represents a pre-created definition that contains the entity and interim table to be used for the transaction restore. This definition is created by the Archive User.
  • Parameter String. A series of carat "^" delimited parameters as a single string that include the following:
    • Transaction Criteria. This represents the unique key of the transaction to be restored. The unique key can be either a primary or a composite key, but it should match the unique key defined in the interim table for the entity selected in the Restore Definition.
    • If a Program Callback is being used and the Program Callback requires input parameters, then additional parameter values are to be included in the Transaction Criteria.
When submitted through the Data Archive UI, the Restore Workbench allows the user to select the Entity, the Interim table, and the selection criteria to use to perform the restore. By pre-creating the Restore Definition, the calling program can hard-code the Restore Definition ID, or a new metadata table can be created that maps specific types of transactions to specific Restore Definitions.
A Program Callback feature allows a secondary program to be executed by the Transaction Restore API itself. The Program Callback can be a PL/SQL stored procedure or a Java program.
The calling program is also responsible for passing the selection criteria to the API. In this case the selection criterion is the specific transaction to be restored. Since all of these values are specific to the archive metadata being used, it is the requirement of the calling program to determine these values, and not the purpose of the API itself to determine these values. If a Program Callback is being used the Program Callback requires input parameters, then the values for these parameters will be appended to the Transaction Restore selection criteria.
The final input parameter will be an indicator to restore the transaction immediately or as part of batch processing to occur later.