ODS Key Concepts
Run Processing
Each Sync between the OIPA data model and the ODS data-model is done by a process named Run. The following types of runs are available.
- Install Run: Takes the snapshot of the Target schema (i.e. ODS Reporting Schema).
- Initial Run: Generates and applies the OIPA DB Schema to the ODS DB.
Note: The Install and Initial runs can be created and executed only one time.
- Subsequent Run: Applies the schema changes of OIPA DB to the ODS DB to maintain consistent schema in the source and the Target databases.
- Alias Run: Applies the user-defined tables names to the ODS tables.
- Rollback Run: Rolls back the applied ODS DB schema changes when a run fails.
Aggregation:
DBMS Scheduler
The scheduler is used to create DBMS jobs that will ensure data sync between the staging database and the target database. The entries are in Cron format and may be used to drive any scheduler. The frequency can be configured in ODS application and can be used anywhere.
ODS Job Scheduler triggers an atomic operation to execute DB jobs in the Staging Database in the frequency set by the user in the ODS utility. For each View in the Staging Database, the Scheduler creates a child job while executing the run. All the child jobs gets executed from the parent job, which is triggered from the Database Scheduled Job set by the user.
Frameworks / Technologies
The following is a list of the most significant frameworks and technologies used by OIPA:
- Spring framework as an application component container
- JPA as a primary method to access persistent data
- Oracle JET framework to implement browser-based user interface
- JAX-RS to implement RESTFul web services