Page Comparison

Step by step instructions for creating the environment and builds for the SSP build and platform.

...

• JDK 1.6 update 21 or later (JDK 1.7 is not supported as of 2012/04)
  
  • http://java.sun.com (openjdk works as well)
• Tomcat 6.X (Tomcat 7 is not supported as of 2012/04)
  
  • http://tomcat.apache.org
• PostgreSQL 9.1 or Microsoft SQL Server 2005-SQL Server 2008 R2
  
  • http://www.postgresql.org
  • http://www.microsoft.com/sqlserver/
• Git
  
  • http://www.git-scm.com
• Sencha SDK
  • http://www.sencha.com/products/sdk-tools/download
• Maven 3.0.3 or later
  
  • http://maven.apache.org
  • Maven is included in the STS package and not required if STS is installed
• Ant 1.8.2 (use this exact version)
  
  • http://ant.apache.org
• Optional Software for developers
  
  • Groovy 1.8.6
    
    • http://groovy.codehaus.org
    • Only if scripts in the Groovy directory are required
  • SpringSource Tool Suite 2.9.0 or greater
    
    • http://www.springsource.org/downloads/sts
    • Only for editing the project source code, not required to simply build the project

  Tip
  title Unix/Linux LInks
  Creating symbolic links for the software packages (STS, Maven, Tomcat, Groovy, etc) makes upgrading the packages simpler Syntax: ln -s  path to executable path to link Example: ln -s /usr/local/springsource/sts-2.9.1.RELEASE /usr/local/sts

...

1. Create the following environment variables with the location of the installation
   
   • JAVA_HOME
   • GROOVY_HOME
   • ANT_HOME
   • MAVEN_HOME
   • M2_HOME
   • TOMCAT_HOME
   • SSP Environment
     • Two installations of SSP can exist on the same server to deploy the application in the web container and to execute unit tests. 
     • The paths can point to the same location as an environment variable on the machine or in the context.xml (see below)via setenv in Tomcat
       
       • SSP_CONFIGDIR

       • SSP_TESTCONFIGDIR

         Info
         title SSP-Open-Source-Project Config Location
         Examples: (Windows) C:\projects\ssp-local\config\ (Unix/MacOS) /opt/projects/ssp-local/config/

2. Add the following locations to the PATH environment variable
   • %MAVEN_HOME%\bin, %JAVA_HOME%\bin, %GROOVY_HOME%\bin, %ANT_HOME%\bin, <git home>\bin, <sencha_home>

2. Database Setup

You can use any supported RDBMS. Follow the steps below to setup the SSP database and login roles for the installation.

...

C:\projects\ssp>git clone git@github.com:Jasig/uPortalSSP-Platform.git

2. Configure Settings

...

Build the full site and database: C:\projects\ssp\SSP-Platform>ant initportal


Other deployment options:

initdb: Drop uPortal tables in the db & recreate them with configured seed data (src/main/data, not including the "quickstart" folder).

deploy-ear: Build entire uPortal (incl. all wars), deploy entire uPortal to Tomcat.

deploy-war: Build & deploy _just the uPortal war_ (i.e. not portlets, etc.).

deployPortletApp: Deploy one (already-built) portlet war file to Tomcat (example ant deploPortletAppdeployPortletApp -DportletApp=..\SSP-Open-Source-Project/target/ssp.war)

...