Page Comparison

...

• 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
  
  • 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:

    Value	Description
    environment.build.hibernate.connection.driver_class	jdbc driver file For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.
    environment.build.hibernate.connection.url	jdbc connection syntax For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.
    environment.build.hibernate.connection.username	jdbc connection database username
    environment.build.hibernate.connection.password	jdbc connection database password
    environment.build.hibernate.dialect	jdbc connection dialect For best results with SQL Server, the JTDS driver included with the Platform installation is recommended.
    environment.build.uportal.server	Hostname and port for your SSP deployment. (Default: localhost:8080)
    environment.build.uportal.protocol	HTTP/S protocol at which end users access your SSP deployment. (Default: http)
    environment.build.uportal.email.fromAddress	Address 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	${environment.build.hibernate.connection.username}
    environment.build.aggreventsdb.connection.password	${environment.build.hibernate.connection.password}
    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.portaldb.test.on.borrow	TRUE
    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:

...