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. Storage Classifications
  24. Appendix A: Datetime and Numeric Formatting
  25. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Step 2. Form the URL that Calls RunUpdateRetention.jsp

Step 2. Form the URL that Calls RunUpdateRetention.jsp

RunUpdateRetention.jsp
schedules the Update Retention Policy job and returns the reference ID.
To call the JSP, form a URL that includes the required parameters. The parameters determine how Data Archive runs the job. For example, on which Data Archive instance the jobs runs, which records you want to update, and the new retention policy.
The URL that calls
RunUpdateRetention.jsp
has the following syntax:
http://<Data Archive Host>:<Data Archive Port>/jsp/RunUpdateRetention.jsp?DEST_REP_NAME=<Destination ILM Repository Name>&ENTITY_ID=<Entity ID>&WHERE_CLAUSE=<WHERE Clause>&EXISTING_POLICY_NAME=<Existing Policy>&NEW_POLICY_NAME=<New Policy>&COMMENTS=<Comments>&USER_NAME=<User Name>&IS_INCLUDE_REFERENCE_TABLES=Yes
The parameters are included in brackets. When you formulate the URL, you insert values for all of the parameters.
The following table describes the parameters to formulate the URL:
Parameter
Description
Host
Name of the Data Archive host.
Port
Name of the Data Archive port.
DEST_REP_NAME or DEST_REP_ID
Destination ILM repository name or repository ID.
ENTITY_ID
Entity ID that you want to modify the retention policy for.
WHERE_CLAUSE
Clause that identifies the records in the entity that you want to change the retention policy for.
EXISTING_POLICY_NAME
Name of the policy that you want to update.
NEW_POLICY_NAME
Name of the new policy that you want to assign to the records.
COMMENTS
Optionally, enter comments that you want to associate with the updated records.
USER_NAME or USER_ID
Data Archive user name or user ID.
Use a user name or user ID that has privileges to update the retention policy. For example, the user should have access to the entity that you want to update.
RELATIVE_TO_DATE
Optionally, if the retention policy does not have column level retention, select a relative date when you assign a different retention policy to an entity. The expiration date equals the relative date plus the retention period.
For example, you select an entity and assign a retention policy that has a retention period of five years. You enter January 1, 2011, as the relative date. The new expiration date is January 1, 2016.
IS_REPORT_REQUIRED
Generates a retention modification report if the value is set to Yes.
Default is No.
IS_PAUSE_AFTER_REPORT
Pauses the job after generating the retention modification report if the value is set to Yes.
Default is No.
IS_INCLUDE_REFERENCE_TABLES
Applies or updates the retention policy on the reference tables. Valid inputs are Yes and No.
Default is No.
The WHERE_CLAUSE parameter uses special formatting for conditions and operators. The following table describes the formatting for conditions or operators:
Condition or Operator
WHERE_CLAUSE Format
>=
###GTEQ###
<=
###LTEQ###
=
###EQ###
<>
###NEQ###
>
###GT###
<
###LT###
In
###IN###
Not In
###NOT_IN###
Is Null
###IS_NULL###
Is Not Null
###NOT_NULL###
Like
###LIKE###
Like (Starts with)
###STARTS_WITH###
Like (Ends with)
###ENDS_WITH###
Like (Contains)
###CONTAINS###
Not Like (Does not start with)
###NOT_START_WITH###
Not Like (Does not end with)
###NOT_END_WITH###
Not Like (Does not contain)
###NOT_CONTAIN###

0 COMMENTS

We’d like to hear from you!