Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create a workspace directory on your file system, e.g. /home/username/jasig/
  2. cd /home/username/jasig
  3. svn co https://source.jasig.org/sa/sched-assist-oraclecalendar/tags/sched-assist-oraclecalendar-1.0.02sched-assist-oraclecalendar
    1. Note: You can replace 'tags/sched-assist-oraclecalendar-1.0.02' in that url with a known release you want to work with, like 'branches/rel-1.0-patches' (not yet available) or 'trunk' (if you need to develop against the very latest).
  4. cd /home/username/jasig/sched-assist-oraclecalendar
  5. cp build-SAMPLE.properties build.properties
  6. Open build.properties in your favorite text editor
  7. Alter the 'oracle.install.home' and 'csdk.jar' to match the locations of your Oracle Calendar install root and the path to the csdk.jar
  8. Alter the 'java_library_path' and 'ld_library_path' to match your environment (comments in the file describe the differences between windows, linux, and solaris)
  9. Execute the following command to install csdk.jar in your local maven repository:

    No Format
    
    ant maven-install-oracle-csdk
    
  10. Now that the csdk jar can be found by the maven build process, install the Scheduling Assistant Oracle Calendar project in your local maven repository:

    No Format
    
    mvn package install
    

Prepping a Tomcat instance for Scheduling Assistant Oracle Calendar

Using the Oracle Calendar SDK native libraries in Tomcat requires additional Tomcat configuration.

  1. In your tomcat 6 install, execute the following:

    No Format
    
    mkdir -p shared/lib
    
  2. This new directory will contain libraries that are loaded by Tomcat's Shared Classloader. Enable the shared classloader by editing:

    No Format
    
    $CATALINA_HOME/conf/catalina.properties
    
  3. Set the value of the 'shared.loader' property to:

    No Format
    
    shared.loader=${catalina.home}/shared/lib/*.jar
    
  4. Back in the Scheduling Assistant Oracle Calendar source tree, open build.properties and edit the tomcat.home property to match your $CATALINA_HOME.
  5. Execute the following command to copy the correct dependencies into your Tomcat's shared/lib:

    No Format
    
    ant deploy-oracle-csdk-and-loader
    

...

  1. Download the sample overlay project at https://mywebspace.wisc.edu/npblair/jasig/my-sched-assist-oraclecalendar-war-1.0.2.zip and unzip on your filesystem.
  2. The first file under your my-sched-assist-oraclecalendar-war directory you will need to edit is at the path:

    No Format
    
    src/main/resources/contexts/integration/oracle-calendar-beans.xml
    
  3. The only "bean" you need to edit in this file is the 'oracleCalendarNodeMap.' Create a map 'entry' for each Oracle Calendar server node you have in your environment, copying the sample entries.
  4. You need to provide a properties file that contains the hostnames, ports, usernames and passwords to integrate with your environment. Directly under your my-sched-assist-oraclecalendar-war directory, open the file with the path:

    No Format
    
    src/main/resources/scheduling-assistant.properties
    
  5. Edit the properties according to the comments. It is critical that you change the values of the ws.username and ws.password properties from the default to avoid being vulnerable to untrusted web service requests. Within this file you will also store the hostname, port, and sysop password for each of your Oracle Calendar server nodes.
  6. Once the properties file matches your environment, save the file.
  7. You should also edit 'src/main/webapp/META-INF/context.xml' to match the JDBC credentials for the database; by default this file contains the credentials for the HSQL database that can be started from the Scheduling Assistant source.
  8. Execute the following command from the root of your my-sched-assist-war directory:

    No Format
    
    mvn package
    
  9. This will download the version of the Scheduling Assistant specified in the pom.xml and add your configuration. The result will be a war file named 'my-scheduling-assistant.war' in the target sub-directory.

...