Configuring Oracle

Before installing the UrbanCode Release server, create an Oracle database. Ideally the database will be installed on a machine other than the one where the server is located.

When you install UrbanCode Release, you will need the connection information, and a user account with at least these minimum privileges:

RESOURCE, CONNECT, CREATE SESSION, and CREATE TABLE.

UrbanCode Release supports the following editions:

  • Oracle Database Enterprise

  • Oracle Database Standard

  • Oracle Database Standard One

  • Oracle Database Express

Version 10g or later is supported for each edition.

To install the database

  1. Obtain the Oracle JDBC driver. The JDBC jar file is included among the Oracle installation files. The driver is unique to the edition you are using.

    Copy the JDBC jar file to tomcat_directory\lib.

  2. Modify the following parameters in the server.properties file:

    	database.type=oracle
    	hibernate.connection.driver_class=oracle.jdbc.driver.OracleDriver
    	hibernate.connection.username=urelease
    	hibernate.connection.password=urelease
    	hibernate.connection.url=jdbc\:mysql\://localhost\:3306/urelease
    

    Important

    Database configuration is done by modifying parameters in the server.properties file located at user_home_directory/.urbancode/urelease/conf. On Unix, the user_home_directory is /home; on Windows it is determined by the user profile, which typically is \Users\current_user. Because UrbanCode Release is deployed as a Tomcat web application, the conf file will not be created until UrbanCode Release is deployed, which means that the configuration changes cannot be made until after initial deployment.

    A typical hibernate.connection.url might be:

    jdbc:oracle:thin:@localhost:1521:XE

    Note

    Initially, the password contains an encrypted string. Overwrite the string with the new password. The first time the password is entered it will be plain text, but will be encrypted the next time UrbanCode Release starts.

  3. When you are fished, restart the Tomcat server.

Note

The database schema to use should be set as the user's default schema.