Skip to end of metadata
Go to start of metadata

System Requirements Reference

Bold properties below are especially important and may require modification.

Property Name



File Locations





Specifies the directory which contains all the XML files describing the database.



Location where the generated SQL files should be placed during the import process.


Directory containing the JDBC driver for your database. Make sure that you actually put the driver version that corresponds to your database server in this directory (particularly if you are using OCI - the version must match exactly). During our testing we have used both the Oracle 10g release 1 and release 2 JDBC drivers. For MySQL, we have used the 5.0.5 version of the driver.



File name patterns that will be scanned when looking for JDBC drivers.

Import Destination





The type of database you will be importing into. Valid values are oracle and mysql.



The fully-qualified class name of your JDBC driver.



The JDBC URL for your database.



The user to use when importing the tables into the database.



Password for the above account.



The name of the schema to import the objects into. MUST be the same as the user. For Oracle, the schema name must be in upper case. In MySQL, you probably want this to be in lower case.

Administrative Properties





Account which will be used to create and destroy users and schemas. On Oracle, this account must have execute privilege on the KULUSER_MAINT_PK package owned by the account specified in the oracle.usermaint.user property. For MySQL, this must be an account with administrative privileges (such as root).



Password for the above account.



Only used for Oracle imports. Account which contains the KULUSER_MAINT_PK package and has permissions to create and drop users and kill sessions.



Password for the above account. Only needed here to run the bootstrap target. (See instructions below.)

Initial Database Setup (Oracle)

  • Review the contents of the four SQL scripts provided
    • Review and adjust user names
    • Review and adjust tablespace names
    • Set passwords (all default to the same as the user ID)
    • In the package, alter the protected users and allowed prefixes as necessary.
  • Run the following scripts as SYS
    • create_kul_developer.sql (creates the KUL_DEVELOPER role)
    • system_grants.sql (grants needed permissions to KULUSERMAINT directly)
  • Complete Setup - Using Ant Scripts
    • Configure the oracle.usermaint.* properties appropriately in
    • Configure the import.admin.user and import.admin.password properties appropriately.
    • Run ant bootstrap

      This will create an administrative user (KULUSER_ADMIN) with execute privilege on the KULUSER_MAINT_PK package in the KULUSERMAINT schema. (as well as create the package) KULUSERMAINT and the KUL_DEVELOPER role must already exist. This process logs in as KULUSERMAINT.

  • Complete Setup - Manual Process
    • Run the following scripts as KULUSERMAINT:
      • create_admin_user.sql (creates the KULUSER_ADMIN user)
      • kuluser_maint_pk.sql (install the user maintenance package)

Initial Database Setup (MySQL)

  • Configure the import.admin.user and import.admin.password properties appropriately.
  • Important: Configure import.admin.url to not include the target schema. Failure to do this will cause the schema/user setup commands to abort.

User Account Setup

  • set the import.admin.* properties to point to an account which can run the user creation commands
    • KULUSER_ADMIN on Oracle
    • root or another account on MySQL
  • If you haven't already, configure the oracle.usermaint.user property to point at the schema where the package was created
  • Use the impex tool to perform database account setup
  • No labels