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

Business Rules

Business Rules

A business rule for Data Archive is the technical representation of a functional requirement. If the rule is the INVOICE IS NOT CLOSED, then there is a field in a table that tells us that an invoice is not closed. Note that rule is INVOICE IS NOT CLOSED as opposed to INVOICE IS CLOSED. Business rules in Data Archive identify transactions that cannot be archived and purged. So the business rules are looking for transaction that FAIL rules. This is important to remember when creating business rules.
As mentioned previously, the enforcement of business rules are tracked in columns in the interim table. That is, each business rule is represented as a column in the interim table. If a sample business rule is INVOICE IS NOT CLOSED, the column in the interim table may be "INVOICE_IS_NOT_CLOSED". We also just described how business rules identify transactions that cannot be archived or purged. If a transaction fails the business rule, then the business rule column is updated with a 1. If a transaction passes the business rule, then the business rule column is updated with a 0. A business rule, therefore, is a SQL UPDATE statement. The UPDATE statement updates transactions in the interim table according to the business rule criteria. Specifically, the UPDATE statement affects transactions that have failed the business rule.