Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. ole-impex- This is the parent module that has sub-modules that contains baseline OLEFS/LS/Rice datasets.
    1. ole-impex-master - This module has all the table definitions (schema.xml) along with data xml files for the base OLEFS/KFS datasets. This doesn't have any Rice related tables or data. For future KFS upgrades, any KFS table changes have to be updated here.
    2. ole-impex-rice - This module strictly contains the Rice table definitions (schema.xml) along with data xml files. The schema.xml that contains all the table definitions are modified for KFS needs, and so wont match with the schema.xml of the rice bootstrap dataset. Any future rice version upgrade changes will need to be accounted here (should come from KFS as KFS had modified rice tables)
    3. ole-impex-ls - This module contains all the table definitions (schema.xml) along with data.xml files for the base OLELS (Circulation and other library functions) datasets. 
  2. ole-liquibase- This module allows injecting data easily by the use of liquibase tooling. Typically all the data files should go in the ole-impex module, but anything that is more demo specific and needs to be ingested for development purposes go here.
    1. ole-liquibase-changeset - This module contains the definitions for any updates that needs to be made to the base OLE schema that contains the base KFS/Rice tables/data. The updates could include creation of new tables, populating with some data etc..
  3. ole-sql - SQL Files under the various sub-modules are auto-generatedby maven commands. The various commands to produce sql statements for both MySQL and Oracle are explained below.

    Warning

    The various SQL files are auto generated by the maven process on the ole-impex and ole-liquibase modules. Do not attempt to manually update the sql files as they will be overridden anytime the build process is run on the ole-impex and ole-liquibase modules.

    1. ole-liquibase-sql - These are auto-generated sql files from the ole-liquibase-changeset module.

       

      No Format
      cd ole-app/ole-db/ole-liquibase/ole-liquibase-changeset
      mvn clean install
      mvn clean process-resources -Psql,mysql
      mvn clean process-resources -Psql,oracle
      cd ole-app
      mvn clean install -DskipTests=true
      cd ole-app/olefs
      mvn clean install -Pdb -Djdbc.dba.username=root -Djdbc.dba.password=root
      mvn initialize -Pdb,oracle -Djdbc.username=OLE -Doracle.dba.url=jdbc:oracle:thin:system/manager@localhost:1521:XE
    2. ole-master-sql - These are auto-generated sql files from the ole-impex-master module.
    3. ole-rice-sql - These are auto generated sql files from the ole-impex-rice module.

      InfoThese auto-generated sql files gets executed by the maven-sql plugin on a database; weather be it MySQL or Oracle. Refer to the DB refresh process in the main Developer's guide

      .

      No Format
      cd into ole-impex
      mvn clean process-resources -Psql -Djdbc.dba.username=[fill me] -Djdbc.dba.password=[fill me]

       

       

  4. ole-workflow - These are files that are put in place as per the KFS/OLEFS workflow definitions. These were manually created to be consumed by the OLEFS application at startup so that all the document definitions along with routing info is available to the application.

OLELS - OLEFS has also a db refresh process similar to OLELS but is not as advanced as in the sql files have to be individually created for both MySQL and Oracle. The Rice tables however are imported directly and executed using the maven tool. 

  1. ole-rice-db - This is the db module that has the sql files for OLELS specific tables. The rice tables are auto-imported and the following maven commands would accomplish that for us;

    No Format
    mvn clean install -Pdb,mysql 

OLEDOCSTORE - Apache Jackrabbit is the underlying content management framework and so the database configuration is taken care by jackrabbit internally when the application is brought up.

  1. repository.xml - This file contains the basic configuration to be used by the jackrabbit framework including specifics on the datasource i.e MySQL, Oracle or File system. 
  2. The very first time the application comes up, jackrabbit will create all the desired tables in the db
    1. subsequently for cleaning the database following actions have to be performed

      Info

      This is assuming that there is a docstore.home property set which essentially points to the location where all the docstore folders are generated by the jackrabbit framework.

      No Format
      delete all the contents under docstore.home directory