Building and Deploying Yaleinfo

Added by Dustin Schultz, last edited by Mary Hunt on Feb 06, 2009  (view change)

You should follow Setting up a local development environment prior to attempting this as many steps are related to the tools you'll set up.

Checking Out YaleInfo

In Eclipse:

  • Window -> Show View -> Other -> type SVN
  • Expand the repository and locate the framework folder
    • Expand YaleInfo and right click on 'trunk' and go to 'checkout..."
    • Click Finish

Alternately you can

Configuring YaleInfo for Build and Deployment

In Eclipse:

  • Open build.properties and edit these properties 
    server.home=## CHANGE ME (i.e. /path/to/apps/apache-tomcat-5.5.26) ##
webapp.hostname=## CHANGE ME (i.e. portal.yale.edu) ##
webapp.logpath=## CHANGE ME (i.e. /path/to/portal/logs) ##

    Refer to the YaleInfo Databases to determine which database corresponds to what environment.

  • Open properties/rdbm.properties and edit these properties 
    jdbcUrl=## CHANGE ME ##
jdbcUser=## CHANGE ME ##
jdbcPassword=## CHANGE ME ##

Building and Deploying YaleInfo for your local environment

In Eclipse:

  • Window -> Show View -> Other -> type Ant
  • In the Ant view, add YaleInfo's build.xml
    • Run the Deploy target
  • Note about warning: unmappable character for encoding urf8
    • In Windows, the eclipse console may stop displaying if it detects an unmappable character.  This may occur when the ant script attempts to compile the edu.columbia.aius.portal.channels.announcements classes.  The ant script will proceed, but will not be reflected in the console.  To correct this problem, do the following:
      • Go to Run/External Tools/Configurations/Ant Build/<your ant build.xml>
      • Under the Common Tab, change the option for Consold encoding from "Default - inherited (utf-8)" to Other ISO-8859-1

Building YaleInfo for a server environment

In Eclipse:

  • Window -> Show View -> Other -> type Ant
  • In the Ant view, add YaleInfo's build.xml
    • Run the dist target

Deploying YaleInfo for a server environment

  • Copy the ROOT.war to the main Tomcat webapps directory (portal1) and let Tomcat explode the war.

Labels

 
(None)