Page Comparison

...

• Maven 3.0.3 or later
  
  • Download Loation: http://maven.apache.org

  • Environment Variable: MAVEN_HOME

    Tip
    title Maven Environment Variables
    MAVEN_HOME= /path/to/your/maven (ie: /usr/local/maven or C:\tools\maven) M2_HOME= /path/to/your/maven (ie: /usr/local/maven or C:\tools\maven) (optional) PATH= append the bin subdirectory to the path statement

• Ant 1.8.2 (use this exact version)
  

  • Download Location: http://ant.apache.org

  • Environment Variable: ANT_HOME

    Tip
    title Ant Environment Variable
    ANT_HOME= /path/to/your/ant (ie: /usr/local/ant or C:\tools\ant) (optional) PATH= append the bin subdirectory to the path statement

• Sencha SDK Tools (current version 2.0.0.0 beta 3
  
  • Download Location: http://www.sencha.com/products/sdk-tools/download/
  • Environment Variable not required, but helpful in adding to path
  • Windows x64 users will also need to install a 32-bit Java SDK/JRE for the sencha build command to work properly (one of the jars in sencha looks for the 32-bit runtime and won't play nicely with the 64-bit SDK/JRE.)
  • See  SSP Sencha Build Tool Usage for additional installation steps on 64-bit OSs
    

     

    Tip
    title Sencha SDK Tools
    PATH= append the Sencha SDK Tools installation directory (not the bin)

• RDBMS (support for PostgreSQL and Microsoft SQL Server)
  
  • PostgreSQL 9.1 or later
    
    • Download Location: http://www.postgresql.org
      
      • On Unix:
        
        • PostgreSQL is available in the package manager of most linux distributions.
          
          • Install it according to the distribution's instructions
        • Ubuntu - https://help.ubuntu.com/11.10/serverguide/C/postgresql.html
      • On Mac:
        
        • PostgreSQL is available via the homebrew package manager or as a download on the postgresql.org site.
      • On Windows:
        
        • PostgreSQL is available as a download on the postgresql.org site.
    • Configure PostgreSQL
      
      • Server Connection
        
        • Launch the PG Admin application
        • In the Object Browser, navigate to and right click on Server Groups -> Servers -> PostgreSQL 9.1 (localhost:5432)
        • Click Connect and the enter the administrator password
      • Login Roles
        
        • In the Object Browser, right click on Login Roles and click New Login Role
          

          • In the Properties tab, enter a Role name of "sspadmin" without the quotes

          • In the Definition tab, enter a Password of "sspadmin" without the quotes

        • In the Object Browser, right click on Login Roles and click New Login Role

          
          

          • In the Properties tab, enter a Role name of "ssp" without the quotes

          • In the Definition tab, enter a Password of "ssp" without the quotes

        • Confirm the new Login Roles exist in the Object Browser
      • Database
        
        • In the Object Browser, right click on Databases and click New Database
          
          • Enter "ssp" without the quotes as the database name
          • Enter "sspadmin" without the quotes as the database owner
        • Confirm the new database exists in the Object Browser
  • Microsoft SQL Server 2008, 2008 R2 or , 2012, 2014
    
    • Server Connection
      
      • Launch the SQL Server Management Studio application
      • Enter your database connection info including administrator account credentials, and click Connect
    • Login Roles
      
      • Navigate to Security->Logins, and right click on New Login
        
        • Login name of "sspadmin" without the quotes
        • Select SQL Server authentication and enter a Password of "sspadmin" without the quote
        • Uncheck Enforce password policy
      • Right click on Logins again, and New Login Role
        
        • Login name of "ssp" without the quotes
        • Select SQL Server authentication and enter a Password of "ssp" without the quote
        • Uncheck Enforce password policy
      • Confirm the new users exist
    • Database
      
      • Navigate to and right click on Databases and click New Database
        
        • Enter "ssp" without the quotes as the database name
      • Confirm the new database exists

  • Run the following SQL to assign user permissions and configure the required database settings

     

    Code Block
    title SQL Server Configurations
    USE [ssp] GO IF NOT EXISTS (SELECT name FROM sys.filegroups WHERE is_default=1 AND name = N'PRIMARY') ALTER DATABASE [ssp] MODIFY FILEGROUP [PRIMARY] DEFAULT GO IF NOT EXISTS (SELECT name FROM sys.database_principals WHERE name = 'ssp') BEGIN CREATE USER [ssp] FOR LOGIN [ssp] EXEC sp_addrolemember N'db_datawriter', N'ssp' EXEC sp_addrolemember N'db_datareader', N'ssp' END GO CREATE USER [sspadmin] FOR LOGIN [sspadmin] GO EXEC sp_addrolemember N'db_owner', N'sspadmin' GO

    Code Block
    For MSSQL 2008 or later: ALTER DATABASE ssp SET ALLOW_SNAPSHOT_ISOLATION ON ALTER DATABASE ssp SET READ_COMMITTED_SNAPSHOT ON

    Also note that for SQLServer the "operational" SSP database user ('ssp' in the example above) must be allowed to execute stored procedures. In most deployments this does not require special configuration, but in the event your security policies are such that that user must be explicitly granted execute permissions on specific stored procs, here are the statements which you would likely need to run. (Use 'dbo' for <schema> unless you know the value should be something else (db_schema from $SSP_CONFIGDIR/ssp-config.properties); use 'ssp' for <ssp-operational-user> unless you've chosen a different name for that account (db_username from $SSP_CONFIGDIR/ssp-config.properties).):

    No Format
    GRANT EXEC on <schema>.REFRESH_MV_DIRECTORY_PERSON to <ssp-operational-user>; GRANT EXEC on <schema>.REFRESH_MV_DIRECTORY_PERSON_BLUE to <ssp-operational-user>; GRANT EXEC on <schema>.update_directory_person_from_view_where_school_id to <ssp-operational-user>; GRANT EXEC on <schema>.update_directory_person_from_view_where_person_id to <ssp-operational-user>;

...

• Create a home directory for the source project files
  
  • Unix/Linux/Mac example: /usr/local/ssp    or  /home/ssp

  • Windows example: C:\ssp   

  Make the directory only readable by the user that is running Tomcat
• Create a directory for the config files
  • Unix/Linux/Mac example: /usr/local/ssp/ssp-config     or    /home/ssp/ssp-localconfig
  • Windows example: C:\ssp\ssp-localsspconfig    
    
    

• Make the directory readable by the user that is running Tomcat 

• Set an Environment Variable for the local configuration file location

  Tip
  SSP_CONFIGDIR=/path/to/your/local-configuration (ie: /usr/local/ssp/ssp-localconfig or C:\ssp\ssp-localconfig)

...

• If this is a server environment typically the project lives in: /opt/ssp/  (*nix) or C:\ssp (Windows). On most non-windows installs and for development installs, it's preferable to unzip Tomcat and not install through the source OS package manager. A /etc/init.d/ssp startup script is also required and before Tomcat starts SSP_CONFIGDIR must be available. For more info see: 

2. Clone the SSP Open Source Project repository from GitHub

The SSP-Open-Source-Project repository in GitHub contains the tool suite for SSP.  Installation begins with cloning the repository.  Two methods exist for obtaining the source files.

C:\\ssp>git clone git@github.com:Jasig/SSP.git

...

    <Parameter name="SSP_CONFIGDIR" value="C:/ssp/ssp-config/ssp-localconfig.properties" /> 

• ssp-config.properties
  
  • The ssp-config.properties file must be modifed for database connectivity and email settings
  • File Location: src/main/config/external to /usr/local/etc/ssp or C:\ssp (depending on the environment

  • Action: copy the  ssp-config.properties file to the local configuration directory SSP_CONFIGDIR. (ie: C:\ssp\ssp-config or \home\ssp\ssp-localconfig)

  • Configuration Values:

db_liquibase_manage_external_database_by_default

db_batchsize 

cacheLifeSpanInMillis 

• logback.xml
  
  • The logback.xml controls the log location and level
  • File Location: src/main/config/external to /usr/local/etc/ssp or C:\ssp (depending on the environment

  • Action: copy the  logback.xml file to the local configuration directory SSP_CONFIGIDR (ie: C:\ssp\ssp-localconfig or /home/ssp/ssp-config)

  • Configuration Values: property file
    
    

  Code Block
  title logback.xml
  <property file="C:/ssp/ssp-localconfig/ssp-configlogback.propertiesxml"

   

  • Additional configuration options
    
    • Adjust the log levels for each log appender as necessary
    • Enable the smtpAppender (disabled by default)
    • Further details regarding managing the logback.xml are included in XML comments within the file

4.  Build SSP

...

• • Common loggers used in past development have been:

C:\ssp\SSP-rel-1-1-0> mvn -Dmaven.test.skip=true install

C:\ssp\SSP-rel-1-1-0> mvn -PSKIP_SENCHA clean install

...

The following configurations are required to build and deploy SSP-Platform.

1. Clone the SSP-Platform repository from GitHub

The SSP-Platform repository in GitHub contains the tool suite for SSP.  Installation begins with cloning the repository.  Two methods exist for obtaining the source files.

C:\\SSP-Platform>git clone -b ssp-master git@github.com:Jasig/uPortal.git

2. Modify SSP-Platform Configuration Files

• build.properties
  
  • The build.properties.sample file is copied or renamed in the current directory.  The parameter defines the location of Tomcat.
  • File Location: (uPortal-ssp-1-0-0)
  • Configuration Values: server.home parameter

server.home=D:/apps/tomcat6

• pom.xml (ONLY for non-JTDS jdbc driver installations on Microsoft SQL Server.  SSP-Platform now supports JTDS driver in the package)
  

  • JDBC driver for SSP-Platform if not using PostgreSQL

    Warning
    The pom.xml should only be changed with extreme care.  This is only required for Microsoft SQL Server installations not using the default JTDS jdbc driver packaged with SSP-Platform.  The parameter defines the location of the driver in the local repository.

  • File Location: (uPortal-ssp-1-0-0)

  • Configuration Values: parameters

  • Action: modify the exist parameters defined for PostgreSQL
    Code Block

    title	JDBC driver identified in the pom.xml

    <!-- The JDBC Driver used by SSP --

    • Code Block
      title

...

C:\ssp\SSP-master>mvn install

• • • Common loggers

      <logger name="org.jasig.ssp.service.external.impl.ExternalPersonServiceImpl" level="debug" /> <!-- Turns on ExternalPersonSync task logging which by default runs at 1a.m. and does magic of updating person records from records --> <logger name="org.jasig.ssp.service.external.impl.ExternalPersonSyncTaskImpl" level="trace" />     <!-- Turns off Coach Sync logging which can be mundane --> <logger name="timing.org.jasig.ssp.service.impl.PersonServiceImpl" level="error" />   <logger name="org.jasig.ssp.service.impl.MapStatusReportCalcTaskImpl" level="debug" />   <!-- Turns off some Email errors which can be annoying if there is no SMTP server spun up--> <logger name="org.jasig.ssp.service.impl.MessageServiceImpl" level="error" />

    <jdbc.groupId>
    </jdbc.groupId>
    <jdbc.artifactId> </jdbc.artifactId> <jdbc.version> </jdbc.version>
  ssp-platform-config.properties
  
  • The ssp-platform-config.properties file must be modifed for database connectivity and email settings
    • Original File Location: ./uportal-war/src/main/resources/properties/ssp-platform-config.default.properties
    • Edit the file and save in the SSP_CONFIGDIR
  • Run-Time File Location: <SSP_CONFIGDIR>/ssp-platform-config.properties
    

     

  • Configuration Values:

    ValueDescriptionenvironment.build.hibernate.connection.driver_classjdbc driver file
    

    For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.

    environment.build.hibernate.connection.urljdbc connection syntax
    

    For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.

    environment.build.hibernate.connection.usernamejdbc connection database usernameenvironment.build.hibernate.connection.passwordjdbc connection database passwordenvironment.build.hibernate.dialectjdbc connection dialect
    

    For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.

    environment.build.uportal.serverHostname and port for your SSP deployment. (Default: localhost:8080)environment.build.uportal.protocolHTTP/S protocol at which end users access your SSP deployment. (Default: http)environment.build.uportal.email.fromAddressAddress from which Platform email will originate. Rarely used. (Default: ssp@university.edu)environment.build.sso.*Several properties which configure inbound LTI and legacy SSO. See documentation specific to those features: SSP LTI Provider and SSP Signed URL SSO. Note that to enable these features environment.build.sso.local.sharedSecret must be set to the same non-empty value as ssp_platform_sso_ticket_service_shared_secret in $SSP_CONFIGDIR/ssp-config.properties(database specific attributes)(default values)environment.build.raweventsdb.connection.driver_class${environment.build.hibernate.connection.driver_class}environment.build.raweventsdb.connection.url${environment.build.hibernate.connection.url}environment.build.raweventsdb.connection.username${environment.build.hibernate.connection.username}environment.build.raweventsdb.connection.password${environment.build.hibernate.connection.password}environment.build.aggreventsdb.connection.driver_class${environment.build.hibernate.connection.driver_class}environment.build.aggreventsdb.connection.url${environment.build.hibernate.connection.url}environment.build.aggreventsdb.connection.username${

    •  

       

       

4.  Build SSP

Use the following command to build the SSP-Open-Source-Project and install it in the local Maven repository (use quotes "-Dmaven.test.skip=true" for Windows):

C:\ssp\SSP\mvn clean -e -U -Dmaven.test.skip=true install

C:\ssp\SSP\mvn -PSKIP_SENCHA -Dmaven.test.skip=true clean -e -U install

...

Anchor
SSP-Platform Build SSP-Platform Build

Configure and Deploy SSP-Platform

The following configurations are required to build and deploy SSP-Platform.

1. Clone the SSP-Platform repository from GitHub

The SSP-Platform repository in GitHub contains the tool suite for SSP.  Installation begins with cloning the repository.  Two methods exist for obtaining the source files.

C:\ssp\git clone -b ssp-master git@github.com:Jasig/uPortal.git

2. Modify SSP-Platform Configuration Files

• build.properties
  
  • The build.properties.sample file is copied or renamed in the current directory.  The parameter defines the location of Tomcat.
  • File Location: (uPortal/)
  • Configuration Values: server.home parameter

server.home=C:/ssp/tomcat

• pom.xml (ONLY for non-JTDS jdbc driver installations on Microsoft SQL Server.  SSP-Platform now supports JTDS driver in the package)
  

  • JDBC driver for SSP-Platform if not using PostgreSQL

    Warning
    The pom.xml should only be changed with extreme care.  This is only required for Microsoft SQL Server installations not using the default JTDS jdbc driver packaged with SSP-Platform.  The parameter defines the location of the driver in the local repository.

  • File Location: (uPortal-ssp-1-0-0)

  • Configuration Values: parameters

  • Action: modify the exist parameters defined for PostgreSQL
    
    

    Code Block
    title JDBC driver identified in the pom.xml
    <!-- The JDBC Driver used by SSP --> <jdbc.groupId> </jdbc.groupId> <jdbc.artifactId> </jdbc.artifactId> <jdbc.version> </jdbc.version>

• ssp-platform-config.properties
  

To install the SSP Demo Data

1. Update SSP & SSP-Platform Source

• Demo data was introduced starting with SSP v1.2.0 and SSP-Platfrom v1.1.0. You'll need to be running those or later versions.

2. Edit the config file

• open 'ssp-config.properties' in your SSP_CONFIGDIR directory 

• edit the line that reads;

  Code Block
  db_liquibase_changelog=classpath:org/jasig/ssp/database/masterChangeLog.xml

  to

  Code Blockdb_liquibase_changelog=classpath:org/jasig/ssp/database/masterChangeLog-demo.xml
  • The ssp-platform-config.properties file must be modifed for database connectivity and email settings
    • Original File Location: ./uportal-war/src/main/resources/properties/ssp-platform-config.default.properties
    • Edit the file and save in the SSP_CONFIGDIR
  • Run-Time File Location: <SSP_CONFIGDIR>/ssp-platform-config.properties
    

     

  • Configuration Values:

    }${password}portaldbteston.borrowraweventsdbinitial.size1minidleraweventsdbmax.active50maxidleraweventsdbmaxwaitraweventsdbabandon.when.percentage.fullraweventsdbremove.abandonedraweventsdbremoveabandoned.timeoutraweventsdbjdbc.interceptorsConnectionState(useEquals=true);ResetAbandonedTimerraweventsdbtestwhile.idleraweventsdbtest.on.borrowTRUEinitialsizeaggreventsdbminidleaggreventsdb.aggreventsdbaggreventsdbaggreventsdbaggreventsdbaggreventsdbaggreventsdbaggreventsdb

    Value	Description
    environment.build.hibernate.connection.driver_class	jdbc driver file (See ssp-config.properties, this uses the same value) For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.
    environment.build.hibernate.connection.url	jdbc connection syntax (See ssp-config.properties, this uses the same value) For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.
    environment.build.hibernate.connection.username	environment.build.aggreventsdb.connection.password		jdbc connection database username (See ssp-config.properties, this uses the same value)
    environment.build.hibernate.connection.	password	jdbc connection database password (See ssp-config.properties, this uses the same value)
    environment.build.portaldb.initial.size1hibernate.dialect	jdbc connection dialect (See ssp-config.properties, this uses the same value) For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.
    environment.build.portaldb.min.idle1uportal.server	Hostname and port for your SSP deployment. (Default: localhost:8080)
    environment.build.portaldb.max.active50uportal.protocol	HTTP/S protocol at which end users access your SSP deployment. (Default: http) (All production should be https!)
    environment.build.portaldbuportal.maxemail.idle	50
    environment.build.portaldb.max.wait	2000
    fromAddress	Address from which Platform email will originate. Rarely used. (Default: ssp@university.edu)
    environment.build.portaldb.abandon.when.percentage.full	70
    environment.build.portaldb.remove.abandoned	TRUE
    sso.*	Several properties which configure inbound LTI and legacy SSO. See documentation specific to those features: SSP LTI Provider and SSP Signed URL SSO. Note that to enable these features environment.build.portaldbsso.remove.abandoned.timeout300local.sharedSecret must be set to the same non-empty value as ssp_platform_sso_ticket_service_shared_secret in $SSP_CONFIGDIR/ssp-config.properties
    (database specific attributes)	(default values)
    environment.build.portaldbraweventsdb.jdbcconnection.interceptors	ConnectionState(useEquals=true);ResetAbandonedTimer	driver_class	${environment.build.portaldbhibernate.test.while.idleTRUEconnection.driver_class}
    environment.build.	raweventsdb.	connection.	TRUE	url	${environment.build.	hibernate.	connection.url}
    environment.build.raweventsdb.	connection.	username	1	${environment.build.	hibernate.	connection.username}
    environment.build.raweventsdb.	connection.	password	50	${environment.build.	hibernate.	connection.	password}	2000
    environment.build.	aggreventsdb.	70	connection.driver_class	${environment.build.	hibernate.	TRUE	connection.driver_class}
    environment.build.	aggreventsdb.	connection.	300	url	${environment.build.	hibernate.	connection.url}
    environment.build.	aggreventsdb.	connection.	TRUE	username	${environment.build.	hibernate.	connection.username}
    environment.build.aggreventsdb.	connection.	password	1	${environment.build.	hibernate.	connection.	password}
    1	environment.build.	portaldb.initial.size	1
    environment.build.portaldb.min.idle	1
    environment.build.portaldb.max.active	50
    environment.build.	portaldb.max.idle	50
    environment.build.	portaldb.max.wait	2000
    environment.build.	portaldb.abandon.when.percentage.full	70
    environment.build.	portaldb.remove.abandoned	TRUE
    environment.build.	portaldb.remove.abandoned.timeout	300
    environment.build.	portaldb.jdbc.interceptors	ConnectionState(useEquals=true);ResetAbandonedTimer
    environment.build.	portaldb.test.while.idle	TRUE
    environment.build.aggreventsdbportaldb.test.on.borrow	TRUE

3.  Build SSP-Platform

Use the following command to build, deploy, and initialize the SSP-Platform project:

*** When running a database initialization ant target (initportal, initdb), you need to specify SSP_CONFIGDIR if it isn't already specified as an env var. 

E.g on *nix.... $> SSP_CONFIGDIR=/opt/ssp/sspconfig ant -Dmaven.test.skip=true clean <target> 

Most Common Commands

- Re/Initialize the SSP-Platform database, then run the equivalent of deploy-ear. Destructive! Appropriate for first-time deployments.

  $> SSP_CONFIGDIR=/opt/ssp/sspconfig ant -Dmaven.test.skip=true clean initportal

- Build and deploy entire SSP-Platform portal, including SSP:

  $> SSP_CONFIGDIR=/opt/ssp/sspconfig ant -Dmaven.test.skip=true clean deploy-ear


Other commonly used ant targets:

testdb: Tests the database settings and connectivity

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

deploy-war: Build & deploy _just the SSP-Platform war_ (i.e. not SSP or other portlets, etc.).

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

• Additional step for Microsoft SQL Server to update column types

• Restart Tomcat

4. Test Deployment

• Start Tomcat and point your browser to http://localhost:8080/ssp-platform
  Click Sign In, and use the credentials user: admin password: admin

...

• • environment.build.raweventsdb.initial.size	1
    environment.build.raweventsdb.min.idle	1
    environment.build.raweventsdb.max.active	50
    environment.build.raweventsdb.max.idle	50
    environment.build.raweventsdb.max.wait	2000
    environment.build.raweventsdb.abandon.when.percentage.full	70
    environment.build.raweventsdb.remove.abandoned	TRUE
    environment.build.raweventsdb.remove.abandoned.timeout	300
    environment.build.raweventsdb.jdbc.interceptors	ConnectionState(useEquals=true);ResetAbandonedTimer
    environment.build.raweventsdb.test.while.idle	TRUE
    environment.build.raweventsdb.test.on.borrow	TRUE
    environment.build.aggreventsdb.initial.size	1
    environment.build.aggreventsdb.min.idle	1
    environment.build.aggreventsdb.max.active	50
    environment.build.aggreventsdb.max.idle	50
    environment.build.aggreventsdb.max.wait	2000
    environment.build.aggreventsdb.abandon.when.percentage.full	70
    environment.build.aggreventsdb.remove.abandoned	TRUE
    environment.build.aggreventsdb.remove.abandoned.timeout	300
    environment.build.aggreventsdb.jdbc.interceptors	ConnectionState(useEquals=true);ResetAbandonedTimer
    environment.build.aggreventsdb.test.while.idle	TRUE
    environment.build.aggreventsdb.test.on.borrow	TRUE

3.  Build SSP-Platform

Use the following command to build, deploy, and initialize the SSP-Platform project:

*** When running a database initialization ant target (initportal, initdb), you need to specify SSP_CONFIGDIR if it isn't already specified as an env var! ***

E.g on *nix.... $> SSP_CONFIGDIR=/opt/ssp/sspconfig ant -Dmaven.test.skip=true clean <target> 
   or 
export SSP_CONFIGDIR=/opt/ssp/sspconfig ; ant -Dmaven.test.skip=true clean <target> 

-----------
Most Common Commands

- Initialize the SSP-Platform database, then runs deploy-ear. (Basically initdb + deploy-ear) *Destructive!* Appropriate for first-time deployments only.

  $> ant -Dmaven.test.skip=true clean initportal

- To Build and deploy the entire SSP-Platform portal and the SSP war to Tomcat (most commonly used since initportal is only used once):

  $> ant -Dmaven.test.skip=true clean deploy-ear


Other commonly used ant targets:

testdb: Tests the database settings and connectivity

initdb: Drop SSP-Platform tables in the db & recreate them with configured seed data (src/main/data, not including the "quickstart" folder). *Destructive if database isn't empty/new!*

deploy-war: Build & deploy _just the SSP-Platform war_ (i.e. not SSP or other portlets, etc.).

deployPortletApp: Deploy one (already-built) portlet war file to Tomcat
  
   $> ant -Dmaven.test.skip=true deployPortletApp -DportletApp=../SSP/target/ssp.war
 

• Additional step for Microsoft SQL Server to update column types

• Restart Tomcat     (../tomcat/bin/shutdown.sh ...  ../tomcat/bin/startup.sh  OR /etc/init.d/ssp/restart   OR  windows service tomcat restart)

4. Test Deployment

• Start Tomcat and point your browser to http://localhost:8080/ssp-platform
  Click Sign In, and use the credentials    user: admin     password: admin
  
  

...

Anchor
ssp-demo-data ssp-demo-data

SSP Demo Data Installation

To install the SSP Demo Data

1. Update SSP & SSP-Platform Source

• Demo data was introduced starting with SSP v1.2.0 and SSP-Platfrom v1.1.0. You'll need to be running those or later versions.

2. Edit the config file

• open 'ssp-config.properties' in your SSP_CONFIGDIR directory 

• edit the line that reads;

  Code Block
  db_liquibase_changelog=classpath:org/jasig/ssp/database/masterChangeLog.xml

  to

  Code Block
  db_liquibase_changelog=classpath:org/jasig/ssp/database/masterChangeLog-apiTest.xml

  Warning
  title Demo Data
  The "masterChangeLog-demo.xml" is old and not supported post SSP 2.2.0. Use the above masterChangeLog-apiTest.xml or the ssp-training data at https://github.com/Jasig/ssp-training for up to date demo, training, and CI data.  If you must use masterChangeLog-demo data see this: Before re-building and restarting Tomact, if you're on SSP v2.0.1 or later you'll likely need to drop some database constraints in order for the demo data to load. See  https://issues.jasig.org/browse/SSP-1877. There is also an open PR that patches the demo data itself as an alternative to manipulating db constraints Rebuild SSP and Deploy Portlet as below. Navigate to the SSP-Platform source directory and run the following command to import the uPortal user files so you can login Code Block ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_demo_entities data-import You should see a long list of various usernames loaded in with this step To test this, login as one of the coaches listed on the SSP Demo Data Documentation page and ensure that you can see students and their associated data listed for the coach you login as.

• Save this change. It will be picked up on the next Tomcat restart. Before doing that, though, if you're on SSP v2.0.1 or later you'll likely need to drop some database constraints in order for the demo data to load. See https://issues.jasig.org/browse/SSP-1877. There is also an open PR that patches the demo data itself as an alternative to manipulating db constraints,restart. 
  
  
  
• 3. Build and Deploy SSP

• Navigate to the SSP source directory and Run the following command to build SSP

  Code Block
  C:\ssp\master>SSP mvn clean -Dmaven.test.skip=true -e -U install

• Navigate to your SSP-Platform source directory and run the following command to deploy SSP

  Code Block
  ant deployPortletApp -DportletApp=(Your SSP source directory)/target/ssp.war

• Stop/Start (or restart) tomcat
• If you watch the catalina.out log file you should see liquibase acquire the changeset and run the changeset for adding demo data. 

4. Import uPortal Userfiles

...

ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_demo_entities data-import

...

• , localhost.log, and/or stderr.log/stdout.log  log file(s) depending on the Tomact instance, you should see liquibase acquire the changeset and run the changeset for adding the demo data. 

   To test this, login as  admin, admin or coach1, password0 and ensure that you can see students and their associated data listed for the coach you login as.

...

Running the API Integration Tests

...

If anything in it is incorrect or unclear, please leave a comment below.