Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Appendix A: Datetime and Numeric Formatting
  24. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Step 4. Add the URL to the External Application Code

Step 4. Add the URL to the External Application Code

Add the URL to the external application code to call the file archive transaction restore API. When the external application calls the API, Data Archive uses the parameters in the URL to run the restore job. Data Archive runs the job immediately.
The API returns either "-1" or a positive integer. "-1" indicates that an error has occurred and you can check the logs for more details. A positive integer is the scheduler ID.
You can use the scheduler ID to retrieve the job ID. Run the following command on the ILM repository to retrieve the job ID: SELECT JOB_ID FROM AM_JOBS where SCHEDULE_ID = <scheduler_ID>
On the
Monitor Jobs
page in Data Archive, file archive transaction restores run through the API are appended with "- API" in the job name.

0 COMMENTS

We’d like to hear from you!