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

Procedure Submit (Without base_url)

Procedure Submit (Without base_url)

If this procedure is used, the customer is expected to edit the package manually, and modify the base_url variable to enter their own base URL (the URL of the Web interface).
Order
Parameter
In/Out
Type
1
defn_id
In
Number
2
param_string
In
Varchar2
3
job_type
In
Varchar2
4
callback
In
Varchar2
5
schedule_id
In
Varchar2
The following table describes the parameters:
Parameter
Description
defn_id
The ID of the Restore Definition that contains the entity and interim table to be used to restore the transaction.
param_string
The column name and value to be used by the Transaction Restore job to restore the transaction. This is the column or columns that comprise the unique key for the transaction. The syntax for the Transaction Key string is:
'CLAIM_ID=12345'
If a composite key is being used, then the columns are separated by the caret (^) symbol:
'CLAIM_ID=12345^CLAIM_TYPE=987'
If the value is a string, then PL/SQL syntax for single quotes must be used:
'CLAIM_ID=12345^CLAIM_TYPE=''ABC'''
If a Program Callback is being used and the program requires input parameters, then those parameter names and values are to be appended to the Transaction Key:
'CLAIM_ID=12345^CLAIM_TYPE=987^CALLBACK_ID=
12AB'
job_type
Type of Job to submit (currently only supports "I" for immediate)
callback
The name of the Program Callback to be executed by the Transaction Restore API. This can be an HTTP or a SQL call. The syntax expected of this parameter is:
sql://program_callback_name($param_name1,$param_name2,… ,$param_nameX)
or
http://web.page.to.call/index.html?$param_name1&param_name2
When using a SQL callback, the sql statement will be executed as the amhome user in the home instance. When formatting this string, it will take any of your parameters (from the parameter string), and it will take these Informatica provided variables:
$ScheduleID or JobID
This refers to the Informatica Unique identifier of the job (as it appears in the Web User Interface).
$ReturnCode
This refers to the result of the job that was executed.
  • C = Complete
  • E = Error
$ReturnText
If the $ReturnCode = E, this will be additional error text from the job.
Using these variables, you can have the XA_TRX_RESTORE_API call any package (from the amhome schema).
For example:
Callback:
sql://call my_callback($JobID, ''$ReturnCode'', ''$ReturnText'', ''$my_id'')
Resulting Callback:
my_callback(111, 'C', '', 'abc')
schedule_id
Output parameter with the result of the schedule.
  • -1 = Error scheduling.
  • Other = The Job ID of the job scheduled.