Warning |
---|
For all existing installations, important upgrade instructions exist in the Release Notes If you are running a SSP version prior to 1.1.1, you are strongly encouraged to upgrade or otherwise apply the reporting subsystem security patches described by SSP-701. If you are running SSP version 2.0.0 or 2.0.0-b3, you are strongly encouraged to upgrade to 2.0.1 or 2.1.0 or 2.2.0 or later or otherwise apply the Confidentiality Level-related patches for the Student Documents tool as described by SSP-1917. Also please take a few minutes to review additional security-related announcements detailed at the top of the SSP space here in Confluence. |
...
- JDK 1.6 update 21 or later (JDK 1.7 is not supported as of 2013/01)
- Download Location: http://java.sun.com (openjdk works as well)Environment
Environment Variable: JAVA_HOME
Tip title Java Environment Variable JAVA_HOME=/path/to/your/java (ie: /usr/local/java or C:\java\jdk)
(optional)
PATH= append the bin subdirectory to the path statement
- Tomcat 6.X (Tomcat 7 is not supported as of 2013/01)
Instructions for installing and configuring Tomcat for the SSP-Platform (uPortal 4.0)
Warning title Tomcat Configuration It is important to complete sections: Environment Variables, Shared Libraries, Shared Sessions, Java Heap. Minimally, the catalina.properties file must contain:
shared.loader=${catalina.base}/shared/lib/*.jar
Additionally, a performance improvement has been experienced by enabling compression in Tomcat
Tip Add compression="force" to the server.xml in the connector like the following:
<Connector port="8080" protocol="HTTP/1.1
connectionTimeout="20000"
redirectPort="8443"
emptySessionPath="true"
compression="force" />
- 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
Download Location: http://www.sencha.com/products/sdk-tools/download
Tip PATH= append the root to the path statement
See SSP Sencha Build Tool Usage for additional installation steps on 64-bit OSs
- 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
- PostgreSQL is available in the package manager of most linux distributions.
- 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.
- On Unix:
- 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
- In the Object Browser, right click on Login Roles and click New Login Role
- 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
- In the Object Browser, right click on Databases and click New Database
- Server Connection
- Download Location: http://www.postgresql.org
- Microsoft SQL Server 2008 R2
- 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
- Navigate to Security->Logins, and right click on New Login
- 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
- Navigate to and right click on Databases and click New Database
- Server Connection
- PostgreSQL 9.1 or later
...
Zip Download |
---|
The source files can be downloaded in a zip file
|
...
- pom.xml (For Microsoft SQL only)
JDBC driver for SSP-Platform if not using PostgreSQL
Warning The pom.xml should only be changed with extreme care. The Microsoft SQL Server jdbc driver needs to be identified in the build. The parameter defines the location of the driver in the local repository.
- File Location:
<platform-src-dir>/pom.xml
Configuration Values: parameters
Action: modify the
jdbc.*
parameters to refer to the JTDS driver instead of the PostgreSQL driver:Code Block title JDBC driver identified in the pom.xml <!-- The JDBC Driver used by SSP --> <jdbc.groupId>net.sourceforge.jtds</jdbc.groupId> <jdbc.artifactId>jtds</jdbc.artifactId> <jdbc.version>1.2.4</jdbc.version>
- local.properties
- The local.properties file must be modifed for database connectivity and email settings
- File Location: <platform-src-dir>/filters/local.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.recommended.
- portal.properties
- This is only required if you are building from the zip file linked to above. If you checked out source code from Git it isn't necessary, but you'll need to make sure 'git' is on your PATH.
- File Location: <platform-src-dir>/uportal-war/src/main/resources/properties/portal.properties
- Configuration Values:
Name | Value |
---|---|
org.jasig.portal.scmRevision | ssp-platform-1.2.1-release |
- pom.xml
- This is only required if you are building from the zip file linked to above. If you checked out source code from Git it isn't necessary, but you'll need to make sure 'git' is on your PATH.
- File Location: <platform-src-dir>/uportal-portlets-overlay/ssp/pom.xml
- Instructions: Find the
buildnumber-maven-plugin
definition and add this below the closingexections
tag: No Format <configuration> <revisionOnScmFailure>ssp-platform-1.2.1-release</revisionOnScmFailure> </configuration>
4. Build SSP-Platform
- Use the following command to build, deploy, and initialize the SSP-Platform project:
...
Warning title Delete Demo Users If you are deploying to a production environment, you You should delete or change the passwords for the uPortal users created for demonstration purposes, including the
admin
userespecially in a production deployment. This can be done through the user interface:Manage Users
->Find an Existing User
-> [Enter user ID from list below] -> [Click result] -> >Delete
or orEdit
, then change password. Demo users:admin
- advisor0
- ken
- student0
- student1
Non-private installs should also either change the
admin
user's password or add some other user to the Portal Administrators group and delete theadmin
user.
If anything in it is incorrect or unclear, please leave a comment below.
...