...
The additional complication to this is that there are actually three components to the full refresh process as will be discussed below.
Rice Data Overview
Since OLE is one of a number of Kuali Rice-based projects, an installation of it also includes certain Rice tables and their associated data. However, storing this data in our master schema leads to maintenance issues when the master structure changes and potential data collisions with other Kuali projects. As such, we rely on the "master" rice datasource directly.
The database impex tool (https://test.kuali.org/svn/kul-cfg-dbs/branches/clover-integration) allows for two database definitions to be overlaid upon one another. So, for a simple install of OLE, where the Rice server is integrated into the application, the impex tool first imports the Rice tables and data into the OLE database and then adds the OLE tables and data.
This, however, does not then include any of the OLE-specific data which needs to be stored in the Rice tables. This includes items such as:
- Workflow Documents (KEW)
- System Parameters (KNS)
- Test Users (KIM)
- Application-Specific Roles (KIM)
- Permissions (KIM)
- Responsibilities (KIM)
To import those, we have two additional steps. (This will hopefully be a single step in the future, when Rice provides for XML import/export for all of these objects.)
- Run Liquibase scripts to add the KNS and KIM data.
- Run the workflow XML Ingester tool (part of Rice) to add the workflow definitions.
The definitions for these items are stored in the following locations:
ole/work/db/rice-data(KIM/KNS)ole/work/workflow(KEW)
After all "normal" import processes are done, these scripts are executed as a final step to load the OLE data into the database.
ole-cfg-dbs Project Structure
| Note |
|---|
|
Rice Data Locations and Structure
| Note |
|---|
|
Document TODO Notes
| Note |
|---|
|