Getting Started with Rice Development

Owned by Emerson David
Last updated: Feb 25, 2010Version comment
2 min read

Overview

Integrating your application with Kuali Rice starts with a knowledge of how the Rice environment works. Upon approval of the Anchor Application Service Managers , the Kuali Rice team will provision the following accounts for you:

  1. Shell account on rice-dev.ucdavis.edu
    • manage your designated Tomcat instance
    • check logs
    • tweak Rice properties
  2. Account on the Rice development database
    • load your own data
    • refresh the entire schema
    • manage schema objects like sequences, stored procedures, etc.
  3. LDAP service account to ldap-test.ucdavis.edu
    • read access to LDAP directory

These accounts will allow you to manage your own Rice development instance.

Managing Your Rice Instance

Accessing Your Shell

  1. Use an SSH2 compliant terminal client like SecureCRT or PuTTY
  2. Your home directory is located in /home/<user name>

Tomcat

  1. Starting/stopping Tomcat instance: 
    [~/]$ sudo /etc/init.d/tomcatX start (or stop)
  2. Tomcat log is at /usr/share/tomcat*X*/logs/catalina.out, where X represents your /wiki/spaces/UCDK/pages/119111827.

Rice Settings

  1. Rice Configuration: /usr/local/rice/dev-X-<Rice version>/rice-config.xml, where X is the name of your application (MIV, KFS, KC, etc.).
  2. Log4J: /usr/local/rice/dev-X-<Rice version>/log4j.properties

Database Access

  1. You will find your database URL and credentials in rice-config.xml. Look for the properties datasource.url, datasource.username and datasource.password

Subversion Prep

Project Structure

  1. Your Rice-specific data will be stored at https://svn.ucdavis.edu/svn/kuali/RiceApplications/<my application>. It is up to you to manage the structure underneath this directory.
  2. The Impex Tool, Rice Bootstrap Data, and Schema Utilities are stored at https://svn.ucdavis.edu/svn/kuali/RiceStandaloneServer/rice-db/tags/<Rice version>. These are needed for managing your schemas.

Checking Out Projects

  1. Create a directory where you will store working copies of files to be checked out from Subversion, such as /home/oracle/subversion/rice-db
  2. Navigate to /home/oracle/subversion/rice-db
  3. Checking out schema-related files 
    [/home/oracle/subversion/rice-db]$ svn co https://svn.ucdavis.edu/svn/kuali/RiceStandaloneServer/rice-db/tags/<Rice version>.

    Under /home/oracle/subversion/rice-db, there will now be a /<Rice version> directory

Refreshing Your Schema

Configure the Impex Tool

  1. Copy /home/oracle/subversion/rice-db/<Rice version>/impex-build.properties.sample to your home directory and rename it to impex-build.properties
  2. Modify /wiki/spaces/UCDK/pages/119111688 to suit. There are helpful schema utility scripts located in /home/oracle/subversion/rice-db/<Rice version>/schema-utils.

    The impex-build.properties.sample file already has pre-import and post-import scripts defined.

Execute the Refresh

  1. Navigate to /home/oracle/subversion/rice-db/<Rice version>/database-impex
  2. Set the classpath to include libraries required by the Impex Tool 
    [/home/oracle/subversion/rice-db/<Rice version>/database-impex}]$ export classpath=./lib;$CLASSPATH
  3. Execute the refresh 
    [/home/oracle/subversion/rice-db/<Rice version>/database-impex}]$ ant import