impex.impex-build.properties.sample Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of impex-legacy-bundle

This project creates a bundle of the Impex legacy tool that is decoupled from Subversion. It creates a jar file that has the exact same binaries, source, directory structure, and layout as the Impex contained inside Subversion. Since it is published as a versioned jar file, it can be referenced in other processes (like the Rice binary release process) without those processes needing the ability to connect back to Subversion to check out the tool. Processes that need access to the legacy Impex tool can thus express a normal maven dependency in order to obtain it.

The newest version!

# -------------------------------------------------------------------
#
#  D A T A B A S E  S E T T I N G S
#
# -------------------------------------------------------------------
# JDBC connection settings. This is used by the JDBCToXML task that
# will create an XML database schema from JDBC metadata. These
# settings are also used by the SQL Ant task to initialize your
# Torque system with the generated SQL.
#
# sameJavaName
#   If true, the JDBC task will set the javaName attribute for the tables
#   and columns to be the same as SQL name.
# -------------------------------------------------------------------

torque.project = kfs
#
# the module and tag to check out from SVN for satellite updates
# these are to be used by a Satellite DBA for automating the refresh of the database
#
# these values are for a Kuali client rice base database
svnroot=https://test.kuali.org/svn/
svn.module=rice-cfg-dbs
# use this Rice source for running with an embedded rice database (normal for development)
svn.base=rice-kuali-client-db/branches/rice-release-1-0-1-br/
# Use the branch below for installing the necessary empty tables when running a separate Rice instance
#svn.base=rice-client-db/branches/rice-release-1-0-1-br/
torque.schema.dir=../../${svn.module}
torque.sql.dir=${torque.schema.dir}/sql

# then, to overlay a KFS/KC/KS database on the base rice database, use the parameters below
# If these parameters are commented out, the impex process will only use the information above
svnroot.2=https://test.kuali.org/svn/
svn.module.2=kfs-cfg-dbs
svn.base.2=trunk
torque.schema.dir.2=../../${svn.module.2}
torque.sql.dir.2=${torque.schema.dir.2}/sql

# Number of parallel threads that will be started for the import process
import.torque.threads=1

#
# where to find JDBC drivers
#
drivers.directory = /java/drivers
drivers.file.pattern=ojdbc*.jar,mysql*.jar
#
# used for packaging exports as necessary
#
target.zip=../kuldemo.zip
source.zip=../kuldemo.zip

#
# You only need to edit these if you are exporting the database to XML
#
export.torque.database = oracle
export.torque.database.driver = oracle.jdbc.OracleDriver
export.torque.database.url = jdbc:oracle:thin:@localhost:1521:XE
export.torque.database.user=kuldba
export.torque.database.schema=KULDBA
export.torque.database.password=kuldba

#
# Modify these to match the database into which you are going to import
#

import.torque.database = oracle
import.torque.database.driver = oracle.jdbc.OracleDriver
import.torque.database.url = jdbc:oracle:thin:@localhost:1521:XE
import.torque.database.user=kuldemo
import.torque.database.schema=KULDEMO
import.torque.database.password=kuldemo

#
# Uncomment these for a local MySQL database
#
#import.torque.database = mysql
#import.torque.database.driver = com.mysql.jdbc.Driver
#import.torque.database.url = jdbc:mysql://localhost:3306/kuldemo
#import.torque.database.user=kuldemo
#import.torque.database.schema=kuldemo
#import.torque.database.password=kuldemo

# uncomment this to skip some of the larger (and mostly unnecessary) tables in the system
# import.exclude.data.pattern=LD_LDGR_ENTR_T.xml,GL_BALANCE_T.xml,GL_ENTRY_T.xml,LD_LDGR_BAL_T.xml,GL_ACCT_BALANCES_T.xml

export.excluded.tables=KRSB_MSG_PYLD_T,KRNS_LOOKUP_RSLT_T,KRIM_PND.*,.*_MT,KRSB_MSG_QUE_T
export.start.table=


# set if you want to use the ant script to set up the users and schemas for the import
# see build.properties for the commands that will be executed

# sample for oracle:
import.admin.user=kuluser_admin
import.admin.password=kuluser_admin

# sample for mysql:
#import.admin.user=root
#import.admin.password=????

# this may need to be different if (like in the case of MySQL) there is a schema name on the URL
# admin commands will not run with that URL if the schema has not yet been created
import.admin.url = ${import.torque.database.url}
# if using MySQL, you will need to remove the schema/database name from the end as below
#import.admin.url=jdbc:mysql://localhost:3306

# these are used by the bootstrapping mechanism
oracle.usermaint.user=kulusermaint
oracle.usermaint.password=kulusermaint

# SQL statements used for creating and dropping users
#
# THESE SHOULD NOT NEED TO BE MODIFIED

# Oracle commands

oracle.drop.user.commands=DECLARE temp NUMBER; BEGIN temp := ${oracle.usermaint.user}.kuluser_maint_pk.drop_user( '${import.torque.database.user}' ); END;

oracle.create.user.commands=DECLARE temp NUMBER; BEGIN temp := ${oracle.usermaint.user}.kuluser_maint_pk.create_user( '${import.torque.database.user}', '${import.torque.database.password}' ); END;

oracle.empty.schema.commands=DECLARE temp NUMBER; BEGIN temp := ${oracle.usermaint.user}.kuluser_maint_pk.recreate_user( '${import.torque.database.user}' ); END;

# MySQL commands

mysql.create.user.command=CREATE USER '${import.torque.database.user}'@'localhost' IDENTIFIED BY '${import.torque.database.password}'

mysql.grant.command=GRANT ALL ON ${import.torque.database.schema}.* TO '${import.torque.database.user}'@'localhost' WITH GRANT OPTION

mysql.create.user.commands=${mysql.create.user.command}

mysql.create.schema.commands=CREATE DATABASE IF NOT EXISTS ${import.torque.database.schema} DEFAULT CHARACTER SET 'utf8' DEFAULT COLLATE 'utf8_bin'\n\
/\n\
${mysql.grant.command}

mysql.drop.schema.commands=DROP DATABASE IF EXISTS ${import.torque.database.schema}