Overview

Running a Rice client application in Embedded Mode means:

• one or more Rice modules - in particular, KEW and KIM - is executing from within the application
• a database is shared by MyInfoVault and the Rice Standalone Server

Access to the Rice Database

A Rice client application requires three schemas:

1. A schema that backs the Rice Standalone Server - generally referred to as the Rice database. The client application uses this schema to store all KEW transactions and expose services on the KSB registry.
2. A Rice-provisioned schema for accessing the Rice database through a role with appropriate permissions (e.g. CRUD on KEW tables, but read-only on KNS tables). Because Rice is "schema-unaware", private synonyms pointing to the objects in the Rice database are created in this schema.
3. A schema that backs the Rice client tables. This is generally hosted in the client application's database. It is used primarily for managing local Rice related Quartz jobs and thus, does not require access to any other schema.

Prerequisites

1. A database account with access to the Rice database
2. LDAP Service Accounts on ldap.ucdavis.edu for dc=ucdavis,dc=edu and {{dc=iet,dc=ucdavis,dc=edu} trees.
3. Procure the UC Davis-specific rice-api and rice-impl JARs and all transitive dependencies using either of the following methods:
   • Download ucd-rice-standalone-server-impl WAR from Artifactory . This WAR contains all dependencies.
   • Maven users: Add ucd-rice-impl as a dependency in your project.

     Code Block
     borderStyle solid title pom.xml
     <repositories> <repository> <id>ietmavenrepositori</id> <name>IET Maven Repository</name> <url>https://psl-95.ucdavis.edu/repo</url> </repository> </repositories> <properties> <ucd-rice-impl.version>[some UCD Rice Implementation version]</ucd-rice-impl.version> </properties> <dependencies> <dependency> <groupId>edu.ucdavis.kuali.rice</groupId> <artifactId>ucd-rice-impl</artifactId> <version>${ucd-rice-impl.version}</version> </dependency> </dependencies>

...